Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be93761ab63146afbc841fcf89d990fb60b4a466b846e51dd8c2576ff588fc6a

Tx prefix hash: 87ee6275a730e73e5b4db402bc16a7884bb756506a2f4eb7ccc1268b247536a4
Tx public key: 6095b66e58d7a5e1a5b728f706646cf4e6e5f4ce7f1b3b1d1adaf3e937c6a16e
Timestamp: 1720938305 Timestamp [UCT]: 2024-07-14 06:25:05 Age [y:d:h:m:s]: 00:189:23:01:25
Block: 1065347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135864 RingCT/type: yes/0
Extra: 016095b66e58d7a5e1a5b728f706646cf4e6e5f4ce7f1b3b1d1adaf3e937c6a16e02110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ea3294a5cbb26295cd1372f7d87541fed3d8396f68a9556ef7358fa87ddae46 0.600000000000 1535892 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": 1065357, "vin": [ { "gen": { "height": 1065347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ea3294a5cbb26295cd1372f7d87541fed3d8396f68a9556ef7358fa87ddae46" } } ], "extra": [ 1, 96, 149, 182, 110, 88, 215, 165, 225, 165, 183, 40, 247, 6, 100, 108, 244, 230, 229, 244, 206, 127, 27, 59, 29, 26, 218, 243, 233, 55, 198, 161, 110, 2, 17, 0, 0, 0, 14, 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