Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6be0916133055a92cd89a6964e942ac4bcd2129f2890056465f228738b8c7b9

Tx prefix hash: 303349b85cd4cbe237dc1630b969ea2ef325e3ec19a6e82ee54abdf53bd53f31
Tx public key: 9154aca5fe0286bcb8d21c83e008cf3e251f98a360b0a42b5fdabfa5f535ceab
Timestamp: 1720138590 Timestamp [UCT]: 2024-07-05 00:16:30 Age [y:d:h:m:s]: 00:257:11:01:28
Block: 1058700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183966 RingCT/type: yes/0
Extra: 019154aca5fe0286bcb8d21c83e008cf3e251f98a360b0a42b5fdabfa5f535ceab02110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4894090c492c5a1bac30dc196d30d2c3dcdc423b4ae4fa09630a9f70316c1580 0.600000000000 1529157 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": 1058710, "vin": [ { "gen": { "height": 1058700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4894090c492c5a1bac30dc196d30d2c3dcdc423b4ae4fa09630a9f70316c1580" } } ], "extra": [ 1, 145, 84, 172, 165, 254, 2, 134, 188, 184, 210, 28, 131, 224, 8, 207, 62, 37, 31, 152, 163, 96, 176, 164, 43, 95, 218, 191, 165, 245, 53, 206, 171, 2, 17, 0, 0, 0, 14, 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