Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e8715574a56daf0bfb6f4d0215bcfc3a76d5f6ccfe97f3da11f7996970f66f

Tx prefix hash: 0881180bc5e68febe229cb4fc7fa663f721f5882e78ceb44752eba13d627e68a
Tx public key: f01bb299f5355b0433ac23399b57f9ff40c3d90e6731903e9c27e3a37964a7d1
Timestamp: 1708026555 Timestamp [UCT]: 2024-02-15 19:49:15 Age [y:d:h:m:s]: 00:332:04:14:04
Block: 958280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237795 RingCT/type: yes/0
Extra: 01f01bb299f5355b0433ac23399b57f9ff40c3d90e6731903e9c27e3a37964a7d10211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bbb0543e5bdac9a238b5422a7b23fef2425cc6f4876c52a02b06134c14316ba 0.600000000000 1417639 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": 958290, "vin": [ { "gen": { "height": 958280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bbb0543e5bdac9a238b5422a7b23fef2425cc6f4876c52a02b06134c14316ba" } } ], "extra": [ 1, 240, 27, 178, 153, 245, 53, 91, 4, 51, 172, 35, 57, 155, 87, 249, 255, 64, 195, 217, 14, 103, 49, 144, 62, 156, 39, 227, 163, 121, 100, 167, 209, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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