Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c473917d92f1eeb47bb31f996d1841b02155a188e7ecf71bac670f1c25229da

Tx prefix hash: 7fdc97471e5f96e315e08ba2b032a01bd7e5145b3e52d2c3f5efa88f2ff108ae
Tx public key: 98abfbb8eccaf4017879b8e04bd2435987f8f9502b0e52947e0f2552ceaf8930
Timestamp: 1703851278 Timestamp [UCT]: 2023-12-29 12:01:18 Age [y:d:h:m:s]: 01:146:04:03:59
Block: 923670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365614 RingCT/type: yes/0
Extra: 0198abfbb8eccaf4017879b8e04bd2435987f8f9502b0e52947e0f2552ceaf89300211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17ce7e3a0071d4aea77e89a03d4e7f41a3a58897eaa1ecde02736473ccf3d255 0.600000000000 1381404 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": 923680, "vin": [ { "gen": { "height": 923670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17ce7e3a0071d4aea77e89a03d4e7f41a3a58897eaa1ecde02736473ccf3d255" } } ], "extra": [ 1, 152, 171, 251, 184, 236, 202, 244, 1, 120, 121, 184, 224, 75, 210, 67, 89, 135, 248, 249, 80, 43, 14, 82, 148, 126, 15, 37, 82, 206, 175, 137, 48, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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