Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a9745aaebdc0cb0d7904efd20129ab73f97d21bddcb424f6dad0acc209e7642

Tx prefix hash: fa6cb38197ffb37bf6a9040d7eef1ce183fc92e71f225a094e6c86714426fa56
Tx public key: 0e9348abdd35fbdcabf3002e7512d9f1091f56edfc30d4d9e142df679758f01d
Timestamp: 1716570890 Timestamp [UCT]: 2024-05-24 17:14:50 Age [y:d:h:m:s]: 00:313:21:06:44
Block: 1029131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224330 RingCT/type: yes/0
Extra: 010e9348abdd35fbdcabf3002e7512d9f1091f56edfc30d4d9e142df679758f01d02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d25b769b6e824021fc4a8fcb6562dc516987543cd79adfa4b17bb226d8a6564 0.600000000000 1497136 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": 1029141, "vin": [ { "gen": { "height": 1029131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d25b769b6e824021fc4a8fcb6562dc516987543cd79adfa4b17bb226d8a6564" } } ], "extra": [ 1, 14, 147, 72, 171, 221, 53, 251, 220, 171, 243, 0, 46, 117, 18, 217, 241, 9, 31, 86, 237, 252, 48, 212, 217, 225, 66, 223, 103, 151, 88, 240, 29, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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