Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97d164db4613d5145e0cae006a5d3229b163bc1f5ca1914e6c418ee78eccfc8a

Tx prefix hash: b7280559bfb2d5706bfc5b8cb65b2419f08076819b2b459399e575ec41e903d9
Tx public key: 33f2c28a7e19ae6d0fadcb13e59c22022748e1844691627594406a0be4387d61
Timestamp: 1636963810 Timestamp [UCT]: 2021-11-15 08:10:10 Age [y:d:h:m:s]: 03:120:07:27:07
Block: 374686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864529 RingCT/type: yes/0
Extra: 0133f2c28a7e19ae6d0fadcb13e59c22022748e1844691627594406a0be4387d6102110000001de9564d6f000000000000000000

1 output(s) for total of 35.197363217000 dcy

stealth address amount amount idx
00: e76918f2964d55a3b426b5863721f42ad23fe366617659527b90cdb5750843e8 35.197363217000 758334 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": 374696, "vin": [ { "gen": { "height": 374686 } } ], "vout": [ { "amount": 35197363217, "target": { "key": "e76918f2964d55a3b426b5863721f42ad23fe366617659527b90cdb5750843e8" } } ], "extra": [ 1, 51, 242, 194, 138, 126, 25, 174, 109, 15, 173, 203, 19, 229, 156, 34, 2, 39, 72, 225, 132, 70, 145, 98, 117, 148, 64, 106, 11, 228, 56, 125, 97, 2, 17, 0, 0, 0, 29, 233, 86, 77, 111, 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