Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7f64b21db0d47a4c55b1986bba9281742283da43f34f1d1b89e82ea8fea457

Tx prefix hash: d2e8597f61cddd6f4394a18ad69848900e6843176d45298c2acaa11773d9f371
Tx public key: f082bb3c3f7cc53825dd0a2901156f52db45e8a46f99b1b8c7a6100e3f760a06
Timestamp: 1718198721 Timestamp [UCT]: 2024-06-12 13:25:21 Age [y:d:h:m:s]: 00:336:20:02:37
Block: 1042633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240729 RingCT/type: yes/0
Extra: 01f082bb3c3f7cc53825dd0a2901156f52db45e8a46f99b1b8c7a6100e3f760a060211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 677330d0ea640dd4345906b70babd2c7000d5c6db10bfc38041fcd4b6b69554b 0.600000000000 1511592 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": 1042643, "vin": [ { "gen": { "height": 1042633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "677330d0ea640dd4345906b70babd2c7000d5c6db10bfc38041fcd4b6b69554b" } } ], "extra": [ 1, 240, 130, 187, 60, 63, 124, 197, 56, 37, 221, 10, 41, 1, 21, 111, 82, 219, 69, 232, 164, 111, 153, 177, 184, 199, 166, 16, 14, 63, 118, 10, 6, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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