Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00412446b33a802556787d87c23336a9a16b8a9e151c69c087e3595995e5035a

Tx prefix hash: 069a7b56ffff1a14210bb7756ee2193ac5364667757270529bd746faf6d1ffd5
Tx public key: 3ddd439d220d63f59d3af56c2a85db91dd7581b5c11ec8feefa9af3c939456ae
Timestamp: 1716742585 Timestamp [UCT]: 2024-05-26 16:56:25 Age [y:d:h:m:s]: 00:309:00:37:17
Block: 1030559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220851 RingCT/type: yes/0
Extra: 013ddd439d220d63f59d3af56c2a85db91dd7581b5c11ec8feefa9af3c939456ae02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cb5a3c53c8064bd3611d2126543b3b935b5c2c599d43a2c994ec3381f9b9336 0.600000000000 1498816 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": 1030569, "vin": [ { "gen": { "height": 1030559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cb5a3c53c8064bd3611d2126543b3b935b5c2c599d43a2c994ec3381f9b9336" } } ], "extra": [ 1, 61, 221, 67, 157, 34, 13, 99, 245, 157, 58, 245, 108, 42, 133, 219, 145, 221, 117, 129, 181, 193, 30, 200, 254, 239, 169, 175, 60, 147, 148, 86, 174, 2, 17, 0, 0, 0, 6, 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