Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d13ef6fa2edf9f9b88dbca9052fe056eb9f23cfeaab20306d6b471def1c37464

Tx prefix hash: bc3f4c058eb5a03cf072a326532fa85928a3aa0fb1ab13431075dc0f957ae61e
Tx public key: 29bdb26da22835850cc62c1dfabfb750c7ec37c72bb822041d1e6e48c264791b
Timestamp: 1583636954 Timestamp [UCT]: 2020-03-08 03:09:14 Age [y:d:h:m:s]: 05:064:06:28:20
Block: 78414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201371 RingCT/type: yes/0
Extra: 0129bdb26da22835850cc62c1dfabfb750c7ec37c72bb822041d1e6e48c264791b021100000014d81c26c0000000000000000000

1 output(s) for total of 337.429197508000 dcy

stealth address amount amount idx
00: 7ac5abe0f065e608aed2358092282f1801930012eecd6e07b7bd6b9193009efd 337.429197508000 143864 of 0

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": 78424, "vin": [ { "gen": { "height": 78414 } } ], "vout": [ { "amount": 337429197508, "target": { "key": "7ac5abe0f065e608aed2358092282f1801930012eecd6e07b7bd6b9193009efd" } } ], "extra": [ 1, 41, 189, 178, 109, 162, 40, 53, 133, 12, 198, 44, 29, 250, 191, 183, 80, 199, 236, 55, 199, 43, 184, 34, 4, 29, 30, 110, 72, 194, 100, 121, 27, 2, 17, 0, 0, 0, 20, 216, 28, 38, 192, 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