Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e13bc1b9a508e5a0beb0b4004316dd9d7ef3bbf2807f6b0d7f756ead83c9ff3

Tx prefix hash: 2fc909f1548eb332460c477e1bc9681fe7e1b17339333dd719a8c16ef5dffd91
Tx public key: 929b790b881d7d5ac54de942eec4fbc49071a7881eb51e33c45fab31f2a6569c
Timestamp: 1739487019 Timestamp [UCT]: 2025-02-13 22:50:19 Age [y:d:h:m:s]: 00:290:08:40:22
Block: 1218682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205288 RingCT/type: yes/0
Extra: 01929b790b881d7d5ac54de942eec4fbc49071a7881eb51e33c45fab31f2a6569c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcab2985057ada4d3ffed78743e95c7f2cf6ced2bd80d02e3bb31a1304f05a6d 0.600000000000 1705501 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": 1218692, "vin": [ { "gen": { "height": 1218682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcab2985057ada4d3ffed78743e95c7f2cf6ced2bd80d02e3bb31a1304f05a6d" } } ], "extra": [ 1, 146, 155, 121, 11, 136, 29, 125, 90, 197, 77, 233, 66, 238, 196, 251, 196, 144, 113, 167, 136, 30, 181, 30, 51, 196, 95, 171, 49, 242, 166, 86, 156, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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