Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6fe46b6dcca8be39a6b0272d6dca537952eee189f26e8f22970a03a9374611fa

Tx prefix hash: 4429ca20809181f6fbcb4dd2056a11da1639a9a8f402b6957205d1e99787aa10
Tx public key: 93968f4a9ae85562f7810e63b8aaa2d818af7caf24e31aea1b641fe07a025661
Timestamp: 1709364086 Timestamp [UCT]: 2024-03-02 07:21:26 Age [y:d:h:m:s]: 01:067:14:28:58
Block: 969386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309325 RingCT/type: yes/0
Extra: 0193968f4a9ae85562f7810e63b8aaa2d818af7caf24e31aea1b641fe07a0256610211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e647f4a92284cb2e7726a77e992aafa4315214ccb1557079c23f61764f615aa 0.600000000000 1429215 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 969396, "vin": [ { "gen": { "height": 969386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e647f4a92284cb2e7726a77e992aafa4315214ccb1557079c23f61764f615aa" } } ], "extra": [ 1, 147, 150, 143, 74, 154, 232, 85, 98, 247, 129, 14, 99, 184, 170, 162, 216, 24, 175, 124, 175, 36, 227, 26, 234, 27, 100, 31, 224, 122, 2, 86, 97, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8