Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a94fe9f6d9a8ffbbacd4c274031afd6caeba5dab867e90530c5055accd9be4f

Tx prefix hash: 077f56ae638e403bb17220535dfe2cb78f91c57ad8738be996fb0cba9f23deab
Tx public key: 86d56781cee8c12b8ef61a7e2ef3af6d9e5271f3ff00817b204ddd4d5b189486
Timestamp: 1705900022 Timestamp [UCT]: 2024-01-22 05:07:02 Age [y:d:h:m:s]: 01:135:12:13:35
Block: 940621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358025 RingCT/type: yes/0
Extra: 0186d56781cee8c12b8ef61a7e2ef3af6d9e5271f3ff00817b204ddd4d5b18948602110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ac8b42e6bc80d641c8b717782502dddff8accfada5bed47c5f7cbe4f65040b5 0.600000000000 1398759 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": 940631, "vin": [ { "gen": { "height": 940621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ac8b42e6bc80d641c8b717782502dddff8accfada5bed47c5f7cbe4f65040b5" } } ], "extra": [ 1, 134, 213, 103, 129, 206, 232, 193, 43, 142, 246, 26, 126, 46, 243, 175, 109, 158, 82, 113, 243, 255, 0, 129, 123, 32, 77, 221, 77, 91, 24, 148, 134, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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