Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8be5b3d7245fb363005c92178886dcf3b45b0e37adf7df902f2390fb6fa69197

Tx prefix hash: aa60b2a6c67fac8e5a91fd9a3fb8a74754c85a6c19eb5595006aa1f14dd2b8e2
Tx public key: c3e8f5678756ad3848f3ad46cbd4802dc69c4444d3cb67affcce79a650e0c490
Timestamp: 1726017631 Timestamp [UCT]: 2024-09-11 01:20:31 Age [y:d:h:m:s]: 00:234:12:28:45
Block: 1107443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167465 RingCT/type: yes/0
Extra: 01c3e8f5678756ad3848f3ad46cbd4802dc69c4444d3cb67affcce79a650e0c49002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efaf7972700914f4e86b0fd8d971710adce0136f60187de708e25e871afe2633 0.600000000000 1585056 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": 1107453, "vin": [ { "gen": { "height": 1107443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efaf7972700914f4e86b0fd8d971710adce0136f60187de708e25e871afe2633" } } ], "extra": [ 1, 195, 232, 245, 103, 135, 86, 173, 56, 72, 243, 173, 70, 203, 212, 128, 45, 198, 156, 68, 68, 211, 203, 103, 175, 252, 206, 121, 166, 80, 224, 196, 144, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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