Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f942b04397a6aa0f38d98c1184ee27f1c92872a684c6a1e908f54a63c2526c

Tx prefix hash: 4cd48a81bdb7c06d03710681da56d0f8820dcb7784a8900c2caafaa1568ac5f0
Tx public key: 19b780877332cde6a1157a0ce9516254c5cdfc00cb745934e055175ea33ef341
Timestamp: 1699712412 Timestamp [UCT]: 2023-11-11 14:20:12 Age [y:d:h:m:s]: 01:132:23:16:05
Block: 889358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356229 RingCT/type: yes/0
Extra: 0119b780877332cde6a1157a0ce9516254c5cdfc00cb745934e055175ea33ef341021100000004faf35c9c000000000000000000

1 output(s) for total of 0.693725654000 dcy

stealth address amount amount idx
00: 49f43f56d735d2abbcce38cb029479374f0930bcd64b90fd02630a69d4a4a24f 0.693725654000 1345353 of 0

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": 889368, "vin": [ { "gen": { "height": 889358 } } ], "vout": [ { "amount": 693725654, "target": { "key": "49f43f56d735d2abbcce38cb029479374f0930bcd64b90fd02630a69d4a4a24f" } } ], "extra": [ 1, 25, 183, 128, 135, 115, 50, 205, 230, 161, 21, 122, 12, 233, 81, 98, 84, 197, 205, 252, 0, 203, 116, 89, 52, 224, 85, 23, 94, 163, 62, 243, 65, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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