Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b705e18f5186f926e844cc05b918b831a298623afae83c5869563d51f5fb0a5d

Tx prefix hash: 083296feba828a03cb08bb8bcfdc59c781e6d6007f73c291411f23cd0dfe64fb
Tx public key: 778cb0cc557491812133c7fc617a7af550668e3979df61406f9ecf8c9e7701c9
Timestamp: 1643312224 Timestamp [UCT]: 2022-01-27 19:37:04 Age [y:d:h:m:s]: 03:277:13:26:04
Block: 426549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 975283 RingCT/type: yes/0
Extra: 01778cb0cc557491812133c7fc617a7af550668e3979df61406f9ecf8c9e7701c9021100000001e778ec4c000000000000000000

1 output(s) for total of 23.695528918000 dcy

stealth address amount amount idx
00: d1c3992f541dc6095c549a7a3ee5165a9445be35009cd7a966d8d5d22430ebea 23.695528918000 835394 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": 426559, "vin": [ { "gen": { "height": 426549 } } ], "vout": [ { "amount": 23695528918, "target": { "key": "d1c3992f541dc6095c549a7a3ee5165a9445be35009cd7a966d8d5d22430ebea" } } ], "extra": [ 1, 119, 140, 176, 204, 85, 116, 145, 129, 33, 51, 199, 252, 97, 122, 122, 245, 80, 102, 142, 57, 121, 223, 97, 64, 111, 158, 207, 140, 158, 119, 1, 201, 2, 17, 0, 0, 0, 1, 231, 120, 236, 76, 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