Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f6d617c2b555c7cd1c203cb607fd68595652d5b8ade54d43a0867082411c916

Tx prefix hash: 8b2cb61f4aeea70487244948c2f7bba807ff68df5ffc1d213369c9a80e07e867
Tx public key: e777d53cb358ede1b67dc810fd48124edf55e803aba1ba538b80f3acaddd694c
Timestamp: 1722786666 Timestamp [UCT]: 2024-08-04 15:51:06 Age [y:d:h:m:s]: 00:318:01:29:59
Block: 1080654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227142 RingCT/type: yes/0
Extra: 01e777d53cb358ede1b67dc810fd48124edf55e803aba1ba538b80f3acaddd694c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8aa26351fb00287ca5ab1b2bb1499420a1b1738a50e0494d0eafd09e0c8896a 0.600000000000 1554099 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": 1080664, "vin": [ { "gen": { "height": 1080654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8aa26351fb00287ca5ab1b2bb1499420a1b1738a50e0494d0eafd09e0c8896a" } } ], "extra": [ 1, 231, 119, 213, 60, 179, 88, 237, 225, 182, 125, 200, 16, 253, 72, 18, 78, 223, 85, 232, 3, 171, 161, 186, 83, 139, 128, 243, 172, 173, 221, 105, 76, 2, 17, 0, 0, 0, 1, 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