Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 565a139a2368e6b952be8286a89c70eb6ae69591a4f610dfba12177ea9be1162

Tx prefix hash: 018f5201c98e125142c246c968d33306767f1e4a1c042bdc114d28dce593a841
Tx public key: 7784c7b364ff6d0eb7537d1f137a333ebe80b6a3e376f07eb06d793a239ea95a
Timestamp: 1713354946 Timestamp [UCT]: 2024-04-17 11:55:46 Age [y:d:h:m:s]: 00:314:06:22:46
Block: 1002463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224644 RingCT/type: yes/0
Extra: 017784c7b364ff6d0eb7537d1f137a333ebe80b6a3e376f07eb06d793a239ea95a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 958dcc3560cf448e195c5e46366d4fd72fafc98ee23e29ca858e4bdf98532c16 0.600000000000 1462979 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": 1002473, "vin": [ { "gen": { "height": 1002463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "958dcc3560cf448e195c5e46366d4fd72fafc98ee23e29ca858e4bdf98532c16" } } ], "extra": [ 1, 119, 132, 199, 179, 100, 255, 109, 14, 183, 83, 125, 31, 19, 122, 51, 62, 190, 128, 182, 163, 227, 118, 240, 126, 176, 109, 121, 58, 35, 158, 169, 90, 2, 17, 0, 0, 0, 3, 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