Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 968a05087e86c15a863f7e61cc334f7dcc5e46f4c82f2ecfd7eca86418193fe5

Tx prefix hash: 1acb10226f8c6eda62c1db1ef6ae3c7aba3ecafb34700e613c959286824c4ea8
Tx public key: 8f198bc93bafcbcf15ee7fda31ec8f1d55c933e99e632ba165479d499fd22c02
Timestamp: 1724726058 Timestamp [UCT]: 2024-08-27 02:34:18 Age [y:d:h:m:s]: 00:245:05:41:35
Block: 1096724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175171 RingCT/type: yes/0
Extra: 018f198bc93bafcbcf15ee7fda31ec8f1d55c933e99e632ba165479d499fd22c02021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ff1b9606e82e5a72da1e35b4ce4f293d4ea9336a8e71563cbeaba8b0ed9f026 0.600000000000 1571919 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": 1096734, "vin": [ { "gen": { "height": 1096724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ff1b9606e82e5a72da1e35b4ce4f293d4ea9336a8e71563cbeaba8b0ed9f026" } } ], "extra": [ 1, 143, 25, 139, 201, 59, 175, 203, 207, 21, 238, 127, 218, 49, 236, 143, 29, 85, 201, 51, 233, 158, 99, 43, 161, 101, 71, 157, 73, 159, 210, 44, 2, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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