Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e2832d2cf6e12e2c74be317da6137187badb7b7de84c673fb293d9ff057308f

Tx prefix hash: edcb26d59d5ef24ae5adf5d00a52ce8fbdb15ba68a615959fc53a020efa9e171
Tx public key: 003c5f0a4472c2dd0b63def93062b6fb7f228e4342a12011826cf1582e0ed7b4
Timestamp: 1726773603 Timestamp [UCT]: 2024-09-19 19:20:03 Age [y:d:h:m:s]: 00:065:22:20:33
Block: 1113709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47128 RingCT/type: yes/0
Extra: 01003c5f0a4472c2dd0b63def93062b6fb7f228e4342a12011826cf1582e0ed7b402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6ce866f05655c99d12186a2da397be62c477b34eef73aaad4ce4a8b3a90ca9a 0.600000000000 1593478 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": 1113719, "vin": [ { "gen": { "height": 1113709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6ce866f05655c99d12186a2da397be62c477b34eef73aaad4ce4a8b3a90ca9a" } } ], "extra": [ 1, 0, 60, 95, 10, 68, 114, 194, 221, 11, 99, 222, 249, 48, 98, 182, 251, 127, 34, 142, 67, 66, 161, 32, 17, 130, 108, 241, 88, 46, 14, 215, 180, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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