Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3d13da8b09049149b4230fce4c66499813227752c524e07b2d2c92b7c9d6168

Tx prefix hash: f0f775182c744186f37eba476e1a1eb4f00b76a315fd789ba246a22aef2ea968
Tx public key: f7bfce013d7be63f4b59678751135247810fef8a76c62f2f9ac5e531fc3df494
Timestamp: 1712328985 Timestamp [UCT]: 2024-04-05 14:56:25 Age [y:d:h:m:s]: 01:039:18:29:35
Block: 993936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289426 RingCT/type: yes/0
Extra: 01f7bfce013d7be63f4b59678751135247810fef8a76c62f2f9ac5e531fc3df49402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4fed0bf16212bd15c00da0b5d30d6813f3bc97bbe31eb4049c1923e74b39481 0.600000000000 1454332 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": 993946, "vin": [ { "gen": { "height": 993936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4fed0bf16212bd15c00da0b5d30d6813f3bc97bbe31eb4049c1923e74b39481" } } ], "extra": [ 1, 247, 191, 206, 1, 61, 123, 230, 63, 75, 89, 103, 135, 81, 19, 82, 71, 129, 15, 239, 138, 118, 198, 47, 47, 154, 197, 229, 49, 252, 61, 244, 148, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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