Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e01b58a1046fbb0d5b60940b05b5317b7573e78eff06048bb7ebce0b3e8c15e3

Tx prefix hash: 5854968b7ab77954449007a08dbd803fff7e577f50644a2bb93a7cba68736ac9
Tx public key: 423e7ce7f6cae64332c43279f9a45b0bed9d4d654d38d3cf4e54254e187d49b9
Timestamp: 1717287031 Timestamp [UCT]: 2024-06-02 00:10:31 Age [y:d:h:m:s]: 01:162:19:27:44
Block: 1035069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374943 RingCT/type: yes/0
Extra: 01423e7ce7f6cae64332c43279f9a45b0bed9d4d654d38d3cf4e54254e187d49b90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a78833f6f455d18b895741bea3a9dc962307d165f52bd38cc5e174241014637 0.600000000000 1503588 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": 1035079, "vin": [ { "gen": { "height": 1035069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a78833f6f455d18b895741bea3a9dc962307d165f52bd38cc5e174241014637" } } ], "extra": [ 1, 66, 62, 124, 231, 246, 202, 230, 67, 50, 196, 50, 121, 249, 164, 91, 11, 237, 157, 77, 101, 77, 56, 211, 207, 78, 84, 37, 78, 24, 125, 73, 185, 2, 17, 0, 0, 0, 2, 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