Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5d707889fcbd398e219cf48ec9f2ded4d03fe9971929f9d53a3b38c5698b471

Tx prefix hash: 88487a93526d54dcb2c0456393908f58de869c1df0e10bee1113b21ef93ac978
Tx public key: 7f20661c087ac398c04794438d02b5dc124b9c911c42300f2fea6b377b7ea758
Timestamp: 1710650409 Timestamp [UCT]: 2024-03-17 04:40:09 Age [y:d:h:m:s]: 01:097:05:21:21
Block: 980062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330313 RingCT/type: yes/0
Extra: 017f20661c087ac398c04794438d02b5dc124b9c911c42300f2fea6b377b7ea758021100000002a5df9d86000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 436fc91aea9cdfed73aec4f461659c43adb7425764968ae601b08dc0b1602fb4 0.600000000000 1440121 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": 980072, "vin": [ { "gen": { "height": 980062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "436fc91aea9cdfed73aec4f461659c43adb7425764968ae601b08dc0b1602fb4" } } ], "extra": [ 1, 127, 32, 102, 28, 8, 122, 195, 152, 192, 71, 148, 67, 141, 2, 181, 220, 18, 75, 156, 145, 28, 66, 48, 15, 47, 234, 107, 55, 123, 126, 167, 88, 2, 17, 0, 0, 0, 2, 165, 223, 157, 134, 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