Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21323f2ffb0a50e3a8332c9f2bb7b3baa719e7a09baf986d19638530c466297d

Tx prefix hash: 419f07ec83d681fa09f793835584a1e5f73c5906b10d3c61739bd5afb183b9ce
Tx public key: 99ef42e9d160cb6d7e7712868a350ea379e8f30c02ec8ad668a22fd79e8d85c2
Timestamp: 1719991027 Timestamp [UCT]: 2024-07-03 07:17:07 Age [y:d:h:m:s]: 00:285:02:25:14
Block: 1057481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203717 RingCT/type: yes/0
Extra: 0199ef42e9d160cb6d7e7712868a350ea379e8f30c02ec8ad668a22fd79e8d85c2021100000002341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07028cfb8ad19db301e0d046d066d1676b243ec10e5527369db9b993e1602326 0.600000000000 1527916 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": 1057491, "vin": [ { "gen": { "height": 1057481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07028cfb8ad19db301e0d046d066d1676b243ec10e5527369db9b993e1602326" } } ], "extra": [ 1, 153, 239, 66, 233, 209, 96, 203, 109, 126, 119, 18, 134, 138, 53, 14, 163, 121, 232, 243, 12, 2, 236, 138, 214, 104, 162, 47, 215, 158, 141, 133, 194, 2, 17, 0, 0, 0, 2, 52, 16, 1, 174, 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