Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d3e8acd5055de06089e449446933db42d12f5a4edf00fe3e222335b3182d0ce

Tx prefix hash: 9eb8d4a741aef3a896a90488148d8d95334bb6974c4b760575cb632a8507e802
Tx public key: 7521cece97f9cddadcf5678e242d5870df08d1c2dbc4ecde7a8292a2c9570601
Timestamp: 1708989528 Timestamp [UCT]: 2024-02-26 23:18:48 Age [y:d:h:m:s]: 01:254:14:29:58
Block: 966279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440688 RingCT/type: yes/0
Extra: 017521cece97f9cddadcf5678e242d5870df08d1c2dbc4ecde7a8292a2c95706010211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8e28188197f011d4ea53d76053dac1eda187d7d0efc5b1ae52007a361ea19bb 0.600000000000 1426036 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": 966289, "vin": [ { "gen": { "height": 966279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8e28188197f011d4ea53d76053dac1eda187d7d0efc5b1ae52007a361ea19bb" } } ], "extra": [ 1, 117, 33, 206, 206, 151, 249, 205, 218, 220, 245, 103, 142, 36, 45, 88, 112, 223, 8, 209, 194, 219, 196, 236, 222, 122, 130, 146, 162, 201, 87, 6, 1, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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