Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68027232e53a713e082924a92082bcfb0717ce1d9c5b2c6485cded8c4e843177

Tx prefix hash: 4a060fb61e5b631ac0a7d453b50eec1f584a2b12fe1bc34cf71944064b44c2d7
Tx public key: 0474c11e5002ebf3484ee0f45dc2cc7af2b438b8fec26e8ac42f9c06fd97b551
Timestamp: 1703638947 Timestamp [UCT]: 2023-12-27 01:02:27 Age [y:d:h:m:s]: 01:341:01:24:16
Block: 921912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502619 RingCT/type: yes/0
Extra: 010474c11e5002ebf3484ee0f45dc2cc7af2b438b8fec26e8ac42f9c06fd97b5510211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae18d68173f627b77ebdb20ff948ba334a963adfdc99b88bf891399a77b22193 0.600000000000 1379606 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": 921922, "vin": [ { "gen": { "height": 921912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae18d68173f627b77ebdb20ff948ba334a963adfdc99b88bf891399a77b22193" } } ], "extra": [ 1, 4, 116, 193, 30, 80, 2, 235, 243, 72, 78, 224, 244, 93, 194, 204, 122, 242, 180, 56, 184, 254, 194, 110, 138, 196, 47, 156, 6, 253, 151, 181, 81, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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