Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e55b25cfce3da705a694718f06c866fd9e9090784e6c186c7bfb9bf95ea9df4a

Tx prefix hash: 3d918d0d726fe4e0c52af88b1ec52285b339a3e16bca7d23940e006b0a36ebd4
Tx public key: aa80f020017713ba20302c6965302990db9e155c11a91e87a0eadb9c102e527f
Timestamp: 1748686159 Timestamp [UCT]: 2025-05-31 10:09:19 Age [y:d:h:m:s]: 00:174:13:21:45
Block: 1294841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122439 RingCT/type: yes/0
Extra: 01aa80f020017713ba20302c6965302990db9e155c11a91e87a0eadb9c102e527f021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab2bcbdc436e627774ddb1c568c667417d50e42e533b2c1d15fec50b25b619d8 0.600000000000 1782338 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": 1294851, "vin": [ { "gen": { "height": 1294841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab2bcbdc436e627774ddb1c568c667417d50e42e533b2c1d15fec50b25b619d8" } } ], "extra": [ 1, 170, 128, 240, 32, 1, 119, 19, 186, 32, 48, 44, 105, 101, 48, 41, 144, 219, 158, 21, 92, 17, 169, 30, 135, 160, 234, 219, 156, 16, 46, 82, 127, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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