Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4833034004778ad35e5a91e06f499fc80a135b8c604168859ab61509e924cd5c

Tx prefix hash: 4dc24996240d31b540d0d14218f35f957854d1f9c0310757053d034641dacc72
Tx public key: c279f71dcd5e5a7b926d314e4bceb2108a71917e1291c7606b59a33510725b0a
Timestamp: 1708296883 Timestamp [UCT]: 2024-02-18 22:54:43 Age [y:d:h:m:s]: 01:052:03:01:39
Block: 960535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298280 RingCT/type: yes/0
Extra: 01c279f71dcd5e5a7b926d314e4bceb2108a71917e1291c7606b59a33510725b0a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3baf0e50dc318a7dfea4eb209bfde9bbd492ec6155c5e7941760b6813d3eef18 0.600000000000 1420106 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": 960545, "vin": [ { "gen": { "height": 960535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3baf0e50dc318a7dfea4eb209bfde9bbd492ec6155c5e7941760b6813d3eef18" } } ], "extra": [ 1, 194, 121, 247, 29, 205, 94, 90, 123, 146, 109, 49, 78, 75, 206, 178, 16, 138, 113, 145, 126, 18, 145, 199, 96, 107, 89, 163, 53, 16, 114, 91, 10, 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