Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00efb202761bc4186d547f510cbf22d2a26ff5bc1fcfd69184315e74a5174518

Tx prefix hash: d55c764b8b45080032ba9e92c7f8b1f88e635cd10ef4eb14147b41f5ff9c3c62
Tx public key: 686486257f6f9ae965fee4e0c088bfb8cd85dc1905a0361ae8ec5c84b82434a9
Timestamp: 1724978395 Timestamp [UCT]: 2024-08-30 00:39:55 Age [y:d:h:m:s]: 00:231:05:30:38
Block: 1098822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165130 RingCT/type: yes/0
Extra: 01686486257f6f9ae965fee4e0c088bfb8cd85dc1905a0361ae8ec5c84b82434a902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e81d83b0c887441dbaa52559b09324218927a1dc53fcca181a4eee901a36c1d 0.600000000000 1574669 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": 1098832, "vin": [ { "gen": { "height": 1098822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e81d83b0c887441dbaa52559b09324218927a1dc53fcca181a4eee901a36c1d" } } ], "extra": [ 1, 104, 100, 134, 37, 127, 111, 154, 233, 101, 254, 228, 224, 192, 136, 191, 184, 205, 133, 220, 25, 5, 160, 54, 26, 232, 236, 92, 132, 184, 36, 52, 169, 2, 17, 0, 0, 0, 5, 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