Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7499be2ea3bf208ee16033a4b7c26576829a7a5536b7ece78b9ef286ce62e4e

Tx prefix hash: 8d64f47f29ff4a77ab95b7015445ec7d77989b1e0add8321768073a80062ea40
Tx public key: e923aa2dcf489fa52f6c3945a4df72e8618602e7198bc07586e5d523b5a3f9a5
Timestamp: 1705927734 Timestamp [UCT]: 2024-01-22 12:48:54 Age [y:d:h:m:s]: 01:346:08:27:14
Block: 940857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506439 RingCT/type: yes/0
Extra: 01e923aa2dcf489fa52f6c3945a4df72e8618602e7198bc07586e5d523b5a3f9a502110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a1a9d1fe0ed89503ccbb0951a746b23c0bb5f32d21dfbf714268b8ba7d048c4 0.600000000000 1398997 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": 940867, "vin": [ { "gen": { "height": 940857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a1a9d1fe0ed89503ccbb0951a746b23c0bb5f32d21dfbf714268b8ba7d048c4" } } ], "extra": [ 1, 233, 35, 170, 45, 207, 72, 159, 165, 47, 108, 57, 69, 164, 223, 114, 232, 97, 134, 2, 231, 25, 139, 192, 117, 134, 229, 213, 35, 181, 163, 249, 165, 2, 17, 0, 0, 0, 12, 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