Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540286b990ba5c140c245ca3dadce0e6dc3c3a3120be1cb67bc5707b2d8378c8

Tx prefix hash: bb7004d679a7e2235af4b637175386a594fca8ff5f0d41f7d21255a3f1548554
Tx public key: 36bf1d7077a83de08c5f0778c2c4cc93f1a7ee70335945934d03623e181589e1
Timestamp: 1705159806 Timestamp [UCT]: 2024-01-13 15:30:06 Age [y:d:h:m:s]: 01:071:18:47:03
Block: 934509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312396 RingCT/type: yes/0
Extra: 0136bf1d7077a83de08c5f0778c2c4cc93f1a7ee70335945934d03623e181589e10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a270c011db73e0d9dcb1b047a89960e635d22e83fcd0e71833f192fdace3db11 0.600000000000 1392523 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": 934519, "vin": [ { "gen": { "height": 934509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a270c011db73e0d9dcb1b047a89960e635d22e83fcd0e71833f192fdace3db11" } } ], "extra": [ 1, 54, 191, 29, 112, 119, 168, 61, 224, 140, 95, 7, 120, 194, 196, 204, 147, 241, 167, 238, 112, 51, 89, 69, 147, 77, 3, 98, 62, 24, 21, 137, 225, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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