Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f06840c1da1df9e114975dbc7ea632d8233d5118915556b2ac626192177f10bb

Tx prefix hash: 886f3c96410e1cd50e7d5355d05f2d7d12941207a3efdcc47a17ce4eeee4a2da
Tx public key: 513ddb8eda57e59f6fcd37fdc38d882ffd5606574870bb169e8aa376e1d3d9f5
Timestamp: 1721073978 Timestamp [UCT]: 2024-07-15 20:06:18 Age [y:d:h:m:s]: 00:258:23:51:20
Block: 1066480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185006 RingCT/type: yes/0
Extra: 01513ddb8eda57e59f6fcd37fdc38d882ffd5606574870bb169e8aa376e1d3d9f5021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8f06153d463b000b0dcbe01d144b8189df5ee89497ab149633cbb6e97086710 0.600000000000 1537091 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": 1066490, "vin": [ { "gen": { "height": 1066480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8f06153d463b000b0dcbe01d144b8189df5ee89497ab149633cbb6e97086710" } } ], "extra": [ 1, 81, 61, 219, 142, 218, 87, 229, 159, 111, 205, 55, 253, 195, 141, 136, 47, 253, 86, 6, 87, 72, 112, 187, 22, 158, 138, 163, 118, 225, 211, 217, 245, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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