Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be0908d78dca38c57f81b121f454e323079a0632f1213e4da03435c60917a79d

Tx prefix hash: c26823c59e8e8b1031f8f745f18d5fad280dac70ae952a90caad2fb67895d884
Tx public key: be7dc15f5338960d79c460fd3c5b624b8cfdff8ed54ec78b02636621022df0f8
Timestamp: 1707342354 Timestamp [UCT]: 2024-02-07 21:45:54 Age [y:d:h:m:s]: 01:020:02:58:08
Block: 952620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275387 RingCT/type: yes/0
Extra: 01be7dc15f5338960d79c460fd3c5b624b8cfdff8ed54ec78b02636621022df0f802110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c56c4516b3ba748293d416ddcbbd0d2e5b56ccf8e4699f4f100578dac3400c6 0.600000000000 1411698 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": 952630, "vin": [ { "gen": { "height": 952620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c56c4516b3ba748293d416ddcbbd0d2e5b56ccf8e4699f4f100578dac3400c6" } } ], "extra": [ 1, 190, 125, 193, 95, 83, 56, 150, 13, 121, 196, 96, 253, 60, 91, 98, 75, 140, 253, 255, 142, 213, 78, 199, 139, 2, 99, 102, 33, 2, 45, 240, 248, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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