Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d193899e6763322aa2a5b214dee645562cc91ef9566760badf6149d43ac34456

Tx prefix hash: 96592d3eb0b3369bca29a595c1ef4c7589d6781a262b8592eab084d864b02416
Tx public key: 3695f88c6207d419a04b7bd41c88e177da76b278c56ec8c71654abc952deb975
Timestamp: 1635599029 Timestamp [UCT]: 2021-10-30 13:03:49 Age [y:d:h:m:s]: 03:007:03:15:00
Block: 363642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 783558 RingCT/type: yes/0
Extra: 013695f88c6207d419a04b7bd41c88e177da76b278c56ec8c71654abc952deb9750211000000014a0f5013000000000000000000

1 output(s) for total of 38.292479037000 dcy

stealth address amount amount idx
00: 8c045f4317bd84577408a2b5c7e5cd2c2ac79ace1eae38a2bde6baaaeded90fb 38.292479037000 739018 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": 363652, "vin": [ { "gen": { "height": 363642 } } ], "vout": [ { "amount": 38292479037, "target": { "key": "8c045f4317bd84577408a2b5c7e5cd2c2ac79ace1eae38a2bde6baaaeded90fb" } } ], "extra": [ 1, 54, 149, 248, 140, 98, 7, 212, 25, 160, 75, 123, 212, 28, 136, 225, 119, 218, 118, 178, 120, 197, 110, 200, 199, 22, 84, 171, 201, 82, 222, 185, 117, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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