Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a733aefb2a1fa49e94f2cfb9bb6fddc96429bde568810caf47156553d832c1e8

Tx prefix hash: 28d9f9147631368db97439f7b0f41154198c2ca8afa817a5598facf9b3088d98
Tx public key: ae60c0949bd2b56e5fb902199983d0de37185dcc710b1225d77b267d3fa48ac1
Timestamp: 1705643773 Timestamp [UCT]: 2024-01-19 05:56:13 Age [y:d:h:m:s]: 01:301:22:30:43
Block: 938514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474625 RingCT/type: yes/0
Extra: 01ae60c0949bd2b56e5fb902199983d0de37185dcc710b1225d77b267d3fa48ac102110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18d8c9751dc1ef7287a5d995ebabe159c4080c4a3a70bec9daac028ace315fd3 0.600000000000 1396584 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": 938524, "vin": [ { "gen": { "height": 938514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18d8c9751dc1ef7287a5d995ebabe159c4080c4a3a70bec9daac028ace315fd3" } } ], "extra": [ 1, 174, 96, 192, 148, 155, 210, 181, 110, 95, 185, 2, 25, 153, 131, 208, 222, 55, 24, 93, 204, 113, 11, 18, 37, 215, 123, 38, 125, 63, 164, 138, 193, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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