Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 896e59913350203843ec8efb57514b34791a4a1ebb7d415a4461906251be57f1

Tx prefix hash: 1beab412964f8e214673eb69298693ec354d73cb4ee60ff5634029e1f8dfe682
Tx public key: c3d10bc0cd7e4f34b5c51d4651a395ca0575647f4fc7ae5d6cb1c3a8138bca95
Timestamp: 1737332796 Timestamp [UCT]: 2025-01-20 00:26:36 Age [y:d:h:m:s]: 00:149:10:31:16
Block: 1201057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106555 RingCT/type: yes/0
Extra: 01c3d10bc0cd7e4f34b5c51d4651a395ca0575647f4fc7ae5d6cb1c3a8138bca95021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47b2068e2402834b8bf9b0c3f732eaabb6205e7affb05bbd93ee544550aedf84 0.600000000000 1687704 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": 1201067, "vin": [ { "gen": { "height": 1201057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47b2068e2402834b8bf9b0c3f732eaabb6205e7affb05bbd93ee544550aedf84" } } ], "extra": [ 1, 195, 209, 11, 192, 205, 126, 79, 52, 181, 197, 29, 70, 81, 163, 149, 202, 5, 117, 100, 127, 79, 199, 174, 93, 108, 177, 195, 168, 19, 139, 202, 149, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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