Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 775db22e0a87a55e7723fd681c4fcdbcb87cd3cd1b03a1f78f411ed3aa400674

Tx prefix hash: 8d68de23673c6410e359b094ebdfa2eac19e4024b0bd0b0fc9d7ed16701b284b
Tx public key: 95c73dd554b13ca5a8b41b7517801ed20959b0e37d59b562202a5e8b1ff4b239
Timestamp: 1737686736 Timestamp [UCT]: 2025-01-24 02:45:36 Age [y:d:h:m:s]: 00:149:10:57:38
Block: 1203987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106491 RingCT/type: yes/0
Extra: 0195c73dd554b13ca5a8b41b7517801ed20959b0e37d59b562202a5e8b1ff4b2390211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0647922ba211bd0b6ee3879d20656a59a4e27c2448bb31e42e2952ec33cea43 0.600000000000 1690668 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": 1203997, "vin": [ { "gen": { "height": 1203987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0647922ba211bd0b6ee3879d20656a59a4e27c2448bb31e42e2952ec33cea43" } } ], "extra": [ 1, 149, 199, 61, 213, 84, 177, 60, 165, 168, 180, 27, 117, 23, 128, 30, 210, 9, 89, 176, 227, 125, 89, 181, 98, 32, 42, 94, 139, 31, 244, 178, 57, 2, 17, 0, 0, 0, 4, 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