Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72a551d6916fad1ca1ae2d00eef3bb739e9f4d0d80ea242cbeac54736c2d00d3

Tx prefix hash: 70f4b22d5132a43000f3572d0a5d5d89e9edda5084934f1335df166512aca30b
Tx public key: e94c523924e912835d27492a25085f193d752a50cdd9c118e0eac06f9baee489
Timestamp: 1648560196 Timestamp [UCT]: 2022-03-29 13:23:16 Age [y:d:h:m:s]: 02:287:08:59:30
Block: 468944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724946 RingCT/type: yes/0
Extra: 01e94c523924e912835d27492a25085f193d752a50cdd9c118e0eac06f9baee48902110000000906faf294000000000000000000

1 output(s) for total of 17.147235445000 dcy

stealth address amount amount idx
00: c287c17438067a59a7e22be05e22a239a3ce4af7230c5750b1eca5e15c75cea6 17.147235445000 887776 of 0

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": 468954, "vin": [ { "gen": { "height": 468944 } } ], "vout": [ { "amount": 17147235445, "target": { "key": "c287c17438067a59a7e22be05e22a239a3ce4af7230c5750b1eca5e15c75cea6" } } ], "extra": [ 1, 233, 76, 82, 57, 36, 233, 18, 131, 93, 39, 73, 42, 37, 8, 95, 25, 61, 117, 42, 80, 205, 217, 193, 24, 224, 234, 192, 111, 155, 174, 228, 137, 2, 17, 0, 0, 0, 9, 6, 250, 242, 148, 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