Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98269d5d1d81ede680ffa399aedaa3c5891fe0aae38c9de9adf7901f8054ebd6

Tx prefix hash: 1990a1d0c396799b620dab03ad4fd827a2555abf331eaec25935f0c2796978f5
Tx public key: b0a2103f6be62166605a91fd3611d9544edd8f914df3aa331d4409db5944771d
Timestamp: 1718190737 Timestamp [UCT]: 2024-06-12 11:12:17 Age [y:d:h:m:s]: 01:172:23:47:40
Block: 1042563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382231 RingCT/type: yes/0
Extra: 01b0a2103f6be62166605a91fd3611d9544edd8f914df3aa331d4409db5944771d0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 043f4341b52b4178ed3078d1fa4854cc11997cc2ada9f9ab4f311db34b6ec8f7 0.600000000000 1511508 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": 1042573, "vin": [ { "gen": { "height": 1042563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "043f4341b52b4178ed3078d1fa4854cc11997cc2ada9f9ab4f311db34b6ec8f7" } } ], "extra": [ 1, 176, 162, 16, 63, 107, 230, 33, 102, 96, 90, 145, 253, 54, 17, 217, 84, 78, 221, 143, 145, 77, 243, 170, 51, 29, 68, 9, 219, 89, 68, 119, 29, 2, 17, 0, 0, 0, 5, 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