Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8e01fb03dd06bf1a6d3b2f3fed5703d7fc40734ca6ea678c54e457d0c8b4a9b

Tx prefix hash: e3d6f0dd71cf9ff881b587a5d2ec528d21d91cbce534ffbcf0a35696de0120d7
Tx public key: 6be646d120abe4d8f6489878dbd5659aa9752278b43b777bc49e665a8e303fda
Timestamp: 1724037573 Timestamp [UCT]: 2024-08-19 03:19:33 Age [y:d:h:m:s]: 00:229:15:27:57
Block: 1091038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163988 RingCT/type: yes/0
Extra: 016be646d120abe4d8f6489878dbd5659aa9752278b43b777bc49e665a8e303fda021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd32cf6da1d660523d6687bc62f407f4cddf193fa366f7a0417253cdb2a1d5e2 0.600000000000 1565663 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": 1091048, "vin": [ { "gen": { "height": 1091038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd32cf6da1d660523d6687bc62f407f4cddf193fa366f7a0417253cdb2a1d5e2" } } ], "extra": [ 1, 107, 230, 70, 209, 32, 171, 228, 216, 246, 72, 152, 120, 219, 213, 101, 154, 169, 117, 34, 120, 180, 59, 119, 123, 196, 158, 102, 90, 142, 48, 63, 218, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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