Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6fbab8adb96b198ac29c2b2ae1d71c72f912d4c0c3d6c5b25a4461fd354c3ce

Tx prefix hash: 34fb381c2f9932a06dbe96b4c211c48e17b0496e1e87abfbef55d8a254322732
Tx public key: 7d1ff494ca86c974cadfc71e6161f895530181ba1a42e3aadceb0616ec9f98e8
Timestamp: 1721256825 Timestamp [UCT]: 2024-07-17 22:53:45 Age [y:d:h:m:s]: 00:178:02:04:21
Block: 1067988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127406 RingCT/type: yes/0
Extra: 017d1ff494ca86c974cadfc71e6161f895530181ba1a42e3aadceb0616ec9f98e802110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 023661f018e1ca0a944f66c9184b70813c1848474e239873b3805a414dd97c72 0.600000000000 1538957 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": 1067998, "vin": [ { "gen": { "height": 1067988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "023661f018e1ca0a944f66c9184b70813c1848474e239873b3805a414dd97c72" } } ], "extra": [ 1, 125, 31, 244, 148, 202, 134, 201, 116, 202, 223, 199, 30, 97, 97, 248, 149, 83, 1, 129, 186, 26, 66, 227, 170, 220, 235, 6, 22, 236, 159, 152, 232, 2, 17, 0, 0, 0, 16, 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