Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5269b42adea1d6c78528fb2c174b9e17b994c5d62e539a4c31972b71d8449614

Tx prefix hash: dd8f307dba4866e3c3d67fcd544a6de832f250b086005323445b4492e26211fc
Tx public key: 11b3de9f067b54111178e35b5aad7a4e3e4e884e50f457feafad09d48c863135
Timestamp: 1704784632 Timestamp [UCT]: 2024-01-09 07:17:12 Age [y:d:h:m:s]: 01:160:09:32:03
Block: 931393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375679 RingCT/type: yes/0
Extra: 0111b3de9f067b54111178e35b5aad7a4e3e4e884e50f457feafad09d48c86313502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ff2aa2280edeac1d109b8193f209b1f65d3bf9463ea040b072a8adc137b4e4e 0.600000000000 1389291 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": 931403, "vin": [ { "gen": { "height": 931393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ff2aa2280edeac1d109b8193f209b1f65d3bf9463ea040b072a8adc137b4e4e" } } ], "extra": [ 1, 17, 179, 222, 159, 6, 123, 84, 17, 17, 120, 227, 91, 90, 173, 122, 78, 62, 78, 136, 78, 80, 244, 87, 254, 175, 173, 9, 212, 140, 134, 49, 53, 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