Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a15083ca7c04df4993a12636b0f8981bdec0c8ccef9b2b4ed56e4d2bafda2d

Tx prefix hash: e135147de15ee7cad07766d681e610fe7169f4befc5777e80ed83bef29a2c2f6
Tx public key: bd706a65b546233e9a06eb6c857da9b1769246ff0a0170fc6cb2a19f092bc1ac
Timestamp: 1704476718 Timestamp [UCT]: 2024-01-05 17:45:18 Age [y:d:h:m:s]: 01:094:04:39:10
Block: 928841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328430 RingCT/type: yes/0
Extra: 01bd706a65b546233e9a06eb6c857da9b1769246ff0a0170fc6cb2a19f092bc1ac0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 499288fc9c1b64915cd47c59d39ddb087b6eb34b8a3e447eda5da5a54bcdbdb8 0.600000000000 1386705 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": 928851, "vin": [ { "gen": { "height": 928841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "499288fc9c1b64915cd47c59d39ddb087b6eb34b8a3e447eda5da5a54bcdbdb8" } } ], "extra": [ 1, 189, 112, 106, 101, 181, 70, 35, 62, 154, 6, 235, 108, 133, 125, 169, 177, 118, 146, 70, 255, 10, 1, 112, 252, 108, 178, 161, 159, 9, 43, 193, 172, 2, 17, 0, 0, 0, 1, 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