Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2145859f2bc3f3c0a34861d03b2bdafb0751b00c8620acb25d5efbb22feb5a95

Tx prefix hash: fbccdc421ea2ddac214b089490d6fc05939017c12ab0a6040135eda1ff208beb
Tx public key: 489771cb5c79bf788dca9c0300ea1f4d4c15e2f9ac124ac67809aef703e42919
Timestamp: 1736456784 Timestamp [UCT]: 2025-01-09 21:06:24 Age [y:d:h:m:s]: 00:103:20:13:01
Block: 1193852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74003 RingCT/type: yes/0
Extra: 01489771cb5c79bf788dca9c0300ea1f4d4c15e2f9ac124ac67809aef703e429190211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a32ed35b920aa4a258bf69d66a122f91e2e3bb1a93091211dbf04e7cf4fd3edf 0.600000000000 1680417 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": 1193862, "vin": [ { "gen": { "height": 1193852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a32ed35b920aa4a258bf69d66a122f91e2e3bb1a93091211dbf04e7cf4fd3edf" } } ], "extra": [ 1, 72, 151, 113, 203, 92, 121, 191, 120, 141, 202, 156, 3, 0, 234, 31, 77, 76, 21, 226, 249, 172, 18, 74, 198, 120, 9, 174, 247, 3, 228, 41, 25, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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