Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d53bdec2fe266daa6f22e893473cf79287e84f60ceb62157bbceb360b1032ffc

Tx prefix hash: 7a845561e050c3853777c68776286610e629dae3eda4f66c451ad7c24dc3acbe
Tx public key: c8e7e3ad25f06c7b17810c4ff95b937968b5461dc3aa1bc5e34a8bcaecc21f06
Timestamp: 1726865901 Timestamp [UCT]: 2024-09-20 20:58:21 Age [y:d:h:m:s]: 00:201:06:23:57
Block: 1114478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143669 RingCT/type: yes/0
Extra: 01c8e7e3ad25f06c7b17810c4ff95b937968b5461dc3aa1bc5e34a8bcaecc21f06021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 447fa90f7114e1b334d38af80ea12bffb82684c86151a44edfc72a7b980570b9 0.600000000000 1594279 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": 1114488, "vin": [ { "gen": { "height": 1114478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "447fa90f7114e1b334d38af80ea12bffb82684c86151a44edfc72a7b980570b9" } } ], "extra": [ 1, 200, 231, 227, 173, 37, 240, 108, 123, 23, 129, 12, 79, 249, 91, 147, 121, 104, 181, 70, 29, 195, 170, 27, 197, 227, 74, 139, 202, 236, 194, 31, 6, 2, 17, 0, 0, 0, 2, 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