Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f50c6368fa63ff863d27d5f4b8e5e45e0e386e7ac2bb7ef7847b22f0e297a5e0

Tx prefix hash: 56ead841ba8276f36554750b72e1dcf443c4868a5e51b7d97f2e5692df11cc56
Tx public key: a4c37cbc3fe1a1c2d06d0fc955dbfab1994e44ad295d08ca53a18440e3e52048
Timestamp: 1716338784 Timestamp [UCT]: 2024-05-22 00:46:24 Age [y:d:h:m:s]: 00:353:22:04:05
Block: 1027207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252973 RingCT/type: yes/0
Extra: 01a4c37cbc3fe1a1c2d06d0fc955dbfab1994e44ad295d08ca53a18440e3e5204802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c1472a38c7e4880e92da2f4d57bb863916208d658c9012e002144d27bb483a7 0.600000000000 1494708 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": 1027217, "vin": [ { "gen": { "height": 1027207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c1472a38c7e4880e92da2f4d57bb863916208d658c9012e002144d27bb483a7" } } ], "extra": [ 1, 164, 195, 124, 188, 63, 225, 161, 194, 208, 109, 15, 201, 85, 219, 250, 177, 153, 78, 68, 173, 41, 93, 8, 202, 83, 161, 132, 64, 227, 229, 32, 72, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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