Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c37d9c4766fa7588162eb9455a5de20e43ebaf5546280cd0a7017510d2acee70

Tx prefix hash: 574bb37507d2d48b04bbf750f66e45740ef1413132be4685231b6f3ec64afe8a
Tx public key: 06c3c05356271985a11004b65e5e65a3a6ea59630089237ba27e4e5440a8c34e
Timestamp: 1715608200 Timestamp [UCT]: 2024-05-13 13:50:00 Age [y:d:h:m:s]: 00:331:08:28:03
Block: 1021166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236821 RingCT/type: yes/0
Extra: 0106c3c05356271985a11004b65e5e65a3a6ea59630089237ba27e4e5440a8c34e021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d7ff4ac262f012b5cb48a4211c907898ba4a2d6ed5e6d7a0bfd7fccb3d1c2e5 0.600000000000 1485397 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": 1021176, "vin": [ { "gen": { "height": 1021166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d7ff4ac262f012b5cb48a4211c907898ba4a2d6ed5e6d7a0bfd7fccb3d1c2e5" } } ], "extra": [ 1, 6, 195, 192, 83, 86, 39, 25, 133, 161, 16, 4, 182, 94, 94, 101, 163, 166, 234, 89, 99, 0, 137, 35, 123, 162, 126, 78, 84, 64, 168, 195, 78, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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