Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea5598c4968d314e2395763a18c934fd2be09d1958a26b7ed86adfef3721b444

Tx prefix hash: 8a9273e160acf485ee9142fec284473e4947d56dbbc5f97152dd6f4b89eb5f47
Tx public key: e636f3f30ca17823fddcf97d4e13b3fb73dfd5800baf6935f837df2e87e239c8
Timestamp: 1728431073 Timestamp [UCT]: 2024-10-08 23:44:33 Age [y:d:h:m:s]: 00:156:09:53:08
Block: 1127449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111587 RingCT/type: yes/0
Extra: 01e636f3f30ca17823fddcf97d4e13b3fb73dfd5800baf6935f837df2e87e239c802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7afb0dcc21173e81edeeaa9f604af7cc1e2bfd979ab0d9c545a24e8e15c0dca9 0.600000000000 1610254 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": 1127459, "vin": [ { "gen": { "height": 1127449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7afb0dcc21173e81edeeaa9f604af7cc1e2bfd979ab0d9c545a24e8e15c0dca9" } } ], "extra": [ 1, 230, 54, 243, 243, 12, 161, 120, 35, 253, 220, 249, 125, 78, 19, 179, 251, 115, 223, 213, 128, 11, 175, 105, 53, 248, 55, 223, 46, 135, 226, 57, 200, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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