Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6931e8a879a3c581da7e4fe6c3e87c826c8cabdef48ec63eb8dba39e55796b

Tx prefix hash: 2c3f80962426285dc0e4f2bcd6ff34dedce98a56db9c820911045d4fb2adcb19
Tx public key: 87f5fe338939cf5b0a793935ce0ccc511fa559b71f3af933d3e34432d8ab696d
Timestamp: 1707391996 Timestamp [UCT]: 2024-02-08 11:33:16 Age [y:d:h:m:s]: 01:068:23:07:39
Block: 953023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310343 RingCT/type: yes/0
Extra: 0187f5fe338939cf5b0a793935ce0ccc511fa559b71f3af933d3e34432d8ab696d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d5ac304396adf9d99d1a0b478f93fa22127398c0f84400c39aa2fbd24d5094d 0.600000000000 1412183 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": 953033, "vin": [ { "gen": { "height": 953023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d5ac304396adf9d99d1a0b478f93fa22127398c0f84400c39aa2fbd24d5094d" } } ], "extra": [ 1, 135, 245, 254, 51, 137, 57, 207, 91, 10, 121, 57, 53, 206, 12, 204, 81, 31, 165, 89, 183, 31, 58, 249, 51, 211, 227, 68, 50, 216, 171, 105, 109, 2, 17, 0, 0, 0, 2, 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