Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c83ddfd3aa225116f4e393988d53536c879e678717bcaf9fcd7dd6e51122d8

Tx prefix hash: 19a05422a3e8fad0205109c84c4046ccb158bc0ca14ec9591274ba6f4258e160
Tx public key: a2b0a7785e7eb581f65a9717ee4779b7394cc7f0cb7bf093f4b9655b062cfc2c
Timestamp: 1704184456 Timestamp [UCT]: 2024-01-02 08:34:16 Age [y:d:h:m:s]: 01:104:22:00:18
Block: 926429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336102 RingCT/type: yes/0
Extra: 01a2b0a7785e7eb581f65a9717ee4779b7394cc7f0cb7bf093f4b9655b062cfc2c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed481e187f34809d9eb54db5b9e1c091d2519cc54ed4963a3a4194c5dd28deca 0.600000000000 1384213 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": 926439, "vin": [ { "gen": { "height": 926429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed481e187f34809d9eb54db5b9e1c091d2519cc54ed4963a3a4194c5dd28deca" } } ], "extra": [ 1, 162, 176, 167, 120, 94, 126, 181, 129, 246, 90, 151, 23, 238, 71, 121, 183, 57, 76, 199, 240, 203, 123, 240, 147, 244, 185, 101, 91, 6, 44, 252, 44, 2, 17, 0, 0, 0, 3, 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