Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00b2d27d0defe8bbc59bd1f44727d6ca78441bbbc1ad160c56eb9d3276b51ccf

Tx prefix hash: 843ea85931e43269bc463822f3baca3549cb4a080c968b3c944e960fb1d249aa
Tx public key: 03cf5ceedc1a2e12d62ca5d923af78d308b801f330d828dd9e307b145898bc5b
Timestamp: 1719747518 Timestamp [UCT]: 2024-06-30 11:38:38 Age [y:d:h:m:s]: 00:353:00:03:26
Block: 1055456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252179 RingCT/type: yes/0
Extra: 0103cf5ceedc1a2e12d62ca5d923af78d308b801f330d828dd9e307b145898bc5b02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 439361d687ab1ab70aa8b63f8101c32ffc7a3dd30e38bbd9b8cec64258671cac 0.600000000000 1525857 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": 1055466, "vin": [ { "gen": { "height": 1055456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "439361d687ab1ab70aa8b63f8101c32ffc7a3dd30e38bbd9b8cec64258671cac" } } ], "extra": [ 1, 3, 207, 92, 238, 220, 26, 46, 18, 214, 44, 165, 217, 35, 175, 120, 211, 8, 184, 1, 243, 48, 216, 40, 221, 158, 48, 123, 20, 88, 152, 188, 91, 2, 17, 0, 0, 0, 4, 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