Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1e0097a27ff1b60468ac95e32d322077791a977e7b3190d157c5d5ed6ffd4a

Tx prefix hash: 72b4e97d0c22a51bfb943b947f6c44b1956fbbe06aff55a940cec97cb8776cdf
Tx public key: 619b92d4419f6814468a3baa271ef3b9a50babadaadaab55888fdb6ba01a8a2f
Timestamp: 1716459720 Timestamp [UCT]: 2024-05-23 10:22:00 Age [y:d:h:m:s]: 01:170:04:33:38
Block: 1028217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380209 RingCT/type: yes/0
Extra: 01619b92d4419f6814468a3baa271ef3b9a50babadaadaab55888fdb6ba01a8a2f0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b5959ef77e9249918322c853558285557875a4d88a8c949ea4cdd6a1d5d4dc 0.600000000000 1496174 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": 1028227, "vin": [ { "gen": { "height": 1028217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b5959ef77e9249918322c853558285557875a4d88a8c949ea4cdd6a1d5d4dc" } } ], "extra": [ 1, 97, 155, 146, 212, 65, 159, 104, 20, 70, 138, 59, 170, 39, 30, 243, 185, 165, 11, 171, 173, 170, 218, 171, 85, 136, 143, 219, 107, 160, 26, 138, 47, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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