Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4b7172dac9a039dea66bebe201c63f643a297d0aa702e3852cefedda091d3e7

Tx prefix hash: f7998b1e97f5e75c66baf7a18ccf355983801c4ac0e90111ebc0992fbaf3bf50
Tx public key: 966501d4a3fef77b52d53641bf6b17b565e24f14a8fb68a6269899989e45f200
Timestamp: 1728745134 Timestamp [UCT]: 2024-10-12 14:58:54 Age [y:d:h:m:s]: 00:161:18:15:01
Block: 1130054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115395 RingCT/type: yes/0
Extra: 01966501d4a3fef77b52d53641bf6b17b565e24f14a8fb68a6269899989e45f200021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5521eaefecf8130ffe8fd4e9e7f6500463d1439d0867a9f8146bcd5dfca9a7f 0.600000000000 1612925 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": 1130064, "vin": [ { "gen": { "height": 1130054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5521eaefecf8130ffe8fd4e9e7f6500463d1439d0867a9f8146bcd5dfca9a7f" } } ], "extra": [ 1, 150, 101, 1, 212, 163, 254, 247, 123, 82, 213, 54, 65, 191, 107, 23, 181, 101, 226, 79, 20, 168, 251, 104, 166, 38, 152, 153, 152, 158, 69, 242, 0, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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