Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d81ad692d6e05c8bdd51c691bbab68ec42be202c59d90f5f9412119fd16c5cc

Tx prefix hash: 3358126991d6e7205c513cfdc7dd45f81d02409f642e0b4c8cf039830d60f5a3
Tx public key: 713046c1806efefa2f246967eb99215ff5a9efb6e398f0e389ff5a853d1b6cff
Timestamp: 1705337070 Timestamp [UCT]: 2024-01-15 16:44:30 Age [y:d:h:m:s]: 01:310:05:43:29
Block: 935980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480550 RingCT/type: yes/0
Extra: 01713046c1806efefa2f246967eb99215ff5a9efb6e398f0e389ff5a853d1b6cff02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f757354a4c61d98562cad2003ff3894175e7260e3d223f5fb0e546ab8a9bd133 0.600000000000 1394002 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": 935990, "vin": [ { "gen": { "height": 935980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f757354a4c61d98562cad2003ff3894175e7260e3d223f5fb0e546ab8a9bd133" } } ], "extra": [ 1, 113, 48, 70, 193, 128, 110, 254, 250, 47, 36, 105, 103, 235, 153, 33, 95, 245, 169, 239, 182, 227, 152, 240, 227, 137, 255, 90, 133, 61, 27, 108, 255, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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