Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbafa1c8b3dcd8165c0a825452efe7bcd56b6a6146896cc8e4a801cb3a977255

Tx prefix hash: a618e1db677ff89f403238d62b13bb0e539f4ebafcf538a961af7f46c72760c6
Tx public key: cc9708e964f240a191cc944d7b43d74e52339b8b451d8caa343b09f960505c31
Timestamp: 1710879303 Timestamp [UCT]: 2024-03-19 20:15:03 Age [y:d:h:m:s]: 01:086:22:43:49
Block: 981954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323067 RingCT/type: yes/0
Extra: 01cc9708e964f240a191cc944d7b43d74e52339b8b451d8caa343b09f960505c3102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d11d3cd27a3ae5afb664c7b36938eb19642246a43947dc13726df332eb13f8a3 0.600000000000 1442057 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": 981964, "vin": [ { "gen": { "height": 981954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d11d3cd27a3ae5afb664c7b36938eb19642246a43947dc13726df332eb13f8a3" } } ], "extra": [ 1, 204, 151, 8, 233, 100, 242, 64, 161, 145, 204, 148, 77, 123, 67, 215, 78, 82, 51, 155, 139, 69, 29, 140, 170, 52, 59, 9, 249, 96, 80, 92, 49, 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