Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97a7be5627351e0086af960f4e75adf6b8fe60e9e53e861d5141104601a860cc

Tx prefix hash: e48653f8f680bb7aad12ba90bb7ed5868acb29a32f30d942b3cf920736d944a4
Tx public key: e8dee54ac1b3eeb46ce0c1c5dda252cb4b0d9c41641aa068dd5ab9b4b5e8c273
Timestamp: 1719006649 Timestamp [UCT]: 2024-06-21 21:50:49 Age [y:d:h:m:s]: 00:279:16:10:53
Block: 1049304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199856 RingCT/type: yes/0
Extra: 01e8dee54ac1b3eeb46ce0c1c5dda252cb4b0d9c41641aa068dd5ab9b4b5e8c27302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 605a8df4268ace4c88bf8392c4c2930d292d82c2e81ac604ef8c17e8fb2c2896 0.600000000000 1519403 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": 1049314, "vin": [ { "gen": { "height": 1049304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "605a8df4268ace4c88bf8392c4c2930d292d82c2e81ac604ef8c17e8fb2c2896" } } ], "extra": [ 1, 232, 222, 229, 74, 193, 179, 238, 180, 108, 224, 193, 197, 221, 162, 82, 203, 75, 13, 156, 65, 100, 26, 160, 104, 221, 90, 185, 180, 181, 232, 194, 115, 2, 17, 0, 0, 0, 5, 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