Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b702f6380ea240e6549c91b24d7e4d313aaec5db3d5676879b6355d9227202f0

Tx prefix hash: 8781b2e2bf80820775d74fc5412d58b4a5886d664ad56caf0b498e207e28c76b
Tx public key: a512b96df3d995977be164df3abab2852d43fd8103d098d5bf053636683a06af
Timestamp: 1717074243 Timestamp [UCT]: 2024-05-30 13:04:03 Age [y:d:h:m:s]: 01:166:23:22:01
Block: 1033300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377927 RingCT/type: yes/0
Extra: 01a512b96df3d995977be164df3abab2852d43fd8103d098d5bf053636683a06af0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a782a3338bcd24d907fa1bd22b7554edb92f1bd1d5dbfb81809d05c4eba409f9 0.600000000000 1501765 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": 1033310, "vin": [ { "gen": { "height": 1033300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a782a3338bcd24d907fa1bd22b7554edb92f1bd1d5dbfb81809d05c4eba409f9" } } ], "extra": [ 1, 165, 18, 185, 109, 243, 217, 149, 151, 123, 225, 100, 223, 58, 186, 178, 133, 45, 67, 253, 129, 3, 208, 152, 213, 191, 5, 54, 54, 104, 58, 6, 175, 2, 17, 0, 0, 0, 3, 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