Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2fc640ef1ae3bc4ff045ff7f04fd668ca9aaca83616665d37c1a56ccc77f398

Tx prefix hash: c49e97c021b9c820728d840e58bb6ce17205de017e095d4df176cadb2e1a3136
Tx public key: cf30a05d2b971ee6b64b7830e32397d837fcdd7b4115d210c1887867e48a409d
Timestamp: 1740741731 Timestamp [UCT]: 2025-02-28 11:22:11 Age [y:d:h:m:s]: 00:302:17:29:40
Block: 1229045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214181 RingCT/type: yes/0
Extra: 01cf30a05d2b971ee6b64b7830e32397d837fcdd7b4115d210c1887867e48a409d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f00fa9416d41b87df4cfc6c405ba072a9799ce32cd697e481b224c10c6374fa9 0.600000000000 1715926 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": 1229055, "vin": [ { "gen": { "height": 1229045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f00fa9416d41b87df4cfc6c405ba072a9799ce32cd697e481b224c10c6374fa9" } } ], "extra": [ 1, 207, 48, 160, 93, 43, 151, 30, 230, 182, 75, 120, 48, 227, 35, 151, 216, 55, 252, 221, 123, 65, 21, 210, 16, 193, 136, 120, 103, 228, 138, 64, 157, 2, 17, 0, 0, 0, 2, 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