Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c97eb53941e0ecfb59ef7068d9961d9e6ae53ebd3a8be057c64013a8c439e87

Tx prefix hash: f41b7fc40b1a343d6518544694f10d991ef17ae5d30caeb9c845cfa0e498a42a
Tx public key: 4bc674e239a2f21e189b2307ce51e2153d982cdad9c74d045e10e8064544f902
Timestamp: 1727035200 Timestamp [UCT]: 2024-09-22 20:00:00 Age [y:d:h:m:s]: 00:062:21:39:11
Block: 1115884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44953 RingCT/type: yes/0
Extra: 014bc674e239a2f21e189b2307ce51e2153d982cdad9c74d045e10e8064544f902021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4effa552863053c1f01ae3d156a1afa5d8a424394e95ac20522e62c0714c1ec 0.600000000000 1596169 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": 1115894, "vin": [ { "gen": { "height": 1115884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4effa552863053c1f01ae3d156a1afa5d8a424394e95ac20522e62c0714c1ec" } } ], "extra": [ 1, 75, 198, 116, 226, 57, 162, 242, 30, 24, 155, 35, 7, 206, 81, 226, 21, 61, 152, 44, 218, 217, 199, 77, 4, 94, 16, 232, 6, 69, 68, 249, 2, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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