Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77e54eb65f5135f2d0e6dc501e4ce4792c910fd905db6c6e3eb1044ebcb04d9c

Tx prefix hash: 770cab142c77f2d865338e5049e3f992302a69b20eaf0afe083cd58b7b9be1a0
Tx public key: 02e9bcc2aa4620bf65c29a136807b8d75e443235f45afa84b24d5dcbc9ab8eb9
Timestamp: 1578936266 Timestamp [UCT]: 2020-01-13 17:24:26 Age [y:d:h:m:s]: 04:345:07:22:57
Block: 44837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136285 RingCT/type: yes/0
Extra: 0102e9bcc2aa4620bf65c29a136807b8d75e443235f45afa84b24d5dcbc9ab8eb902110000000f4943cd9f000000000000000000

1 output(s) for total of 435.950566977000 dcy

stealth address amount amount idx
00: d4b67f26f759ca7c92d228e663386061814a1d7d6c64c53ecb67061e73863f2b 435.950566977000 81714 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": 44847, "vin": [ { "gen": { "height": 44837 } } ], "vout": [ { "amount": 435950566977, "target": { "key": "d4b67f26f759ca7c92d228e663386061814a1d7d6c64c53ecb67061e73863f2b" } } ], "extra": [ 1, 2, 233, 188, 194, 170, 70, 32, 191, 101, 194, 154, 19, 104, 7, 184, 215, 94, 68, 50, 53, 244, 90, 250, 132, 178, 77, 93, 203, 201, 171, 142, 185, 2, 17, 0, 0, 0, 15, 73, 67, 205, 159, 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