Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd4b1daf10e8748ce9dac8adb369d581874ce6a2a24451cda63e4c84aec17e94

Tx prefix hash: 46f5ab3321337395378782459e9367663b88cf61c48b6a1d0a803685579b1644
Tx public key: 759ff281cc9c7ef4ab6ce3a91ac17b25032ead7e8c7f5ee396d36eda75cb757c
Timestamp: 1706660503 Timestamp [UCT]: 2024-01-31 00:21:43 Age [y:d:h:m:s]: 01:092:04:32:35
Block: 946949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326978 RingCT/type: yes/0
Extra: 01759ff281cc9c7ef4ab6ce3a91ac17b25032ead7e8c7f5ee396d36eda75cb757c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 226a9654b7416d85c13e5e0c39e13ba45cc25cb4a7cd3d9f6d2d2a2306912ec1 0.600000000000 1405295 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": 946959, "vin": [ { "gen": { "height": 946949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "226a9654b7416d85c13e5e0c39e13ba45cc25cb4a7cd3d9f6d2d2a2306912ec1" } } ], "extra": [ 1, 117, 159, 242, 129, 204, 156, 126, 244, 171, 108, 227, 169, 26, 193, 123, 37, 3, 46, 173, 126, 140, 127, 94, 227, 150, 211, 110, 218, 117, 203, 117, 124, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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