Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77d16de2d816bfa94f67b9acc3b34cef57b01dbf99568833bd8bd451c6ca7691

Tx prefix hash: b492cd506ff12c6a7f62aececc6285e22135651a5387627549c8a0d76006c615
Tx public key: d06d7ae0ac03671e1a8c50fb7f0c674536164c95212dd192aa89612dc9353e41
Timestamp: 1743722360 Timestamp [UCT]: 2025-04-03 23:19:20 Age [y:d:h:m:s]: 00:034:09:55:51
Block: 1253728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24621 RingCT/type: yes/0
Extra: 01d06d7ae0ac03671e1a8c50fb7f0c674536164c95212dd192aa89612dc9353e410211000000054060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c68e6d949dbca3cdfcbf5b1723c15123db65606e1706f361587bf3a25519e7c8 0.600000000000 1740809 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": 1253738, "vin": [ { "gen": { "height": 1253728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68e6d949dbca3cdfcbf5b1723c15123db65606e1706f361587bf3a25519e7c8" } } ], "extra": [ 1, 208, 109, 122, 224, 172, 3, 103, 30, 26, 140, 80, 251, 127, 12, 103, 69, 54, 22, 76, 149, 33, 45, 209, 146, 170, 137, 97, 45, 201, 53, 62, 65, 2, 17, 0, 0, 0, 5, 64, 96, 246, 210, 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