Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351538d1e754a5e10cfde7fe3b192cc00d58b3f2a5e6b5cbd09336ca77436172

Tx prefix hash: 40376c6185e95fbdda6596d7fad8ca02a1725ad8c10f4cdf3b244c3ef69ba3e7
Tx public key: de19abdff7862dd72911b59346f0cd240170f2d325024f8857585f64359b9a85
Timestamp: 1721685154 Timestamp [UCT]: 2024-07-22 21:52:34 Age [y:d:h:m:s]: 00:237:13:28:40
Block: 1071511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169731 RingCT/type: yes/0
Extra: 01de19abdff7862dd72911b59346f0cd240170f2d325024f8857585f64359b9a8502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e67b8b956b40b2807f3797c0e9ecf535e3b4893764782e4aeae73e494445d857 0.600000000000 1543770 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": 1071521, "vin": [ { "gen": { "height": 1071511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e67b8b956b40b2807f3797c0e9ecf535e3b4893764782e4aeae73e494445d857" } } ], "extra": [ 1, 222, 25, 171, 223, 247, 134, 45, 215, 41, 17, 181, 147, 70, 240, 205, 36, 1, 112, 242, 211, 37, 2, 79, 136, 87, 88, 95, 100, 53, 155, 154, 133, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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