Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a230900ffd808e9dd1ec56fd4eed1adc6df4e1f9bb61c2c724a177007bcdf412

Tx prefix hash: 1a7cb85159c751aae96c6cceab0aad9816b5530eb84dfb450b345f9f9f80ff5a
Tx public key: f74757a604e2ca268e06defd41782b2c8d311041351e068ae3e87abc9d7f821d
Timestamp: 1724209988 Timestamp [UCT]: 2024-08-21 03:13:08 Age [y:d:h:m:s]: 00:231:19:11:46
Block: 1092464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165524 RingCT/type: yes/0
Extra: 01f74757a604e2ca268e06defd41782b2c8d311041351e068ae3e87abc9d7f821d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2cfae42e593adf09937dadb67a3364cb66c8169ebc593e7c07ebf5e78449b9b 0.600000000000 1567217 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": 1092474, "vin": [ { "gen": { "height": 1092464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2cfae42e593adf09937dadb67a3364cb66c8169ebc593e7c07ebf5e78449b9b" } } ], "extra": [ 1, 247, 71, 87, 166, 4, 226, 202, 38, 142, 6, 222, 253, 65, 120, 43, 44, 141, 49, 16, 65, 53, 30, 6, 138, 227, 232, 122, 188, 157, 127, 130, 29, 2, 17, 0, 0, 0, 2, 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