Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f081f106d3cd30fb308f7674eb284a0742c70ecbabcfb80a2ec910d23bb088b5

Tx prefix hash: ef7ad6ba9dcf13ed2ce37af8df85c61a24794cc6c34900a9106ee16a93d62186
Tx public key: c1cd764fad368a266a8bad35b5dbdad20420a7c32be569d545f86dcb7a345b6d
Timestamp: 1724991779 Timestamp [UCT]: 2024-08-30 04:22:59 Age [y:d:h:m:s]: 00:290:09:54:24
Block: 1098927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207358 RingCT/type: yes/0
Extra: 01c1cd764fad368a266a8bad35b5dbdad20420a7c32be569d545f86dcb7a345b6d02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d7e2b10960f3442486bedb53d0bb600c3deb6c2bf0ac4c3ed1ba6b0b5d2f59d 0.600000000000 1574812 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": 1098937, "vin": [ { "gen": { "height": 1098927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d7e2b10960f3442486bedb53d0bb600c3deb6c2bf0ac4c3ed1ba6b0b5d2f59d" } } ], "extra": [ 1, 193, 205, 118, 79, 173, 54, 138, 38, 106, 139, 173, 53, 181, 219, 218, 210, 4, 32, 167, 195, 43, 229, 105, 213, 69, 248, 109, 203, 122, 52, 91, 109, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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