Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03061877f324e4abeef1d974520353e4ad6b3239300a18afa4e7d4c281c58036

Tx prefix hash: 9e6f05a88a854ce4dece772bd028bcf1dfc40a0b438db1b3098d3b34eeb01450
Tx public key: 4e17f46d5e601ea94d4dbd9af83a43feb16b06fb081ed357f2bf17896ac63c47
Timestamp: 1721480151 Timestamp [UCT]: 2024-07-20 12:55:51 Age [y:d:h:m:s]: 00:306:23:18:40
Block: 1069823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219355 RingCT/type: yes/0
Extra: 014e17f46d5e601ea94d4dbd9af83a43feb16b06fb081ed357f2bf17896ac63c470211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 804c138c94e58681df7900429485cc207d1c3ae3cb1d5e870c5ea7fe8e24fa89 0.600000000000 1541408 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": 1069833, "vin": [ { "gen": { "height": 1069823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "804c138c94e58681df7900429485cc207d1c3ae3cb1d5e870c5ea7fe8e24fa89" } } ], "extra": [ 1, 78, 23, 244, 109, 94, 96, 30, 169, 77, 77, 189, 154, 248, 58, 67, 254, 177, 107, 6, 251, 8, 30, 211, 87, 242, 191, 23, 137, 106, 198, 60, 71, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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