Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f48a1bebf2df94a7f57376714cc52f74ab3e879cd9fde89ab64b073708ebd7b

Tx prefix hash: 49bc9eac440a376d4ea5ef90cd4f938d6c5bb4258c3d81450e2579d8d8a40f72
Tx public key: f4c5683914f760177f13ffa118ad666fcfdba042db7967d768a4e5f73a0e2ab8
Timestamp: 1697293945 Timestamp [UCT]: 2023-10-14 14:32:25 Age [y:d:h:m:s]: 01:167:06:16:21
Block: 869514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380570 RingCT/type: yes/0
Extra: 01f4c5683914f760177f13ffa118ad666fcfdba042db7967d768a4e5f73a0e2ab802110000001ae6d27f9c000000000000000000

1 output(s) for total of 0.807122016000 dcy

stealth address amount amount idx
00: 670a1f189330a9fcc5f5882af188751b419680c4a321abf641fe21e0d082af16 0.807122016000 1324361 of 0

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": 869524, "vin": [ { "gen": { "height": 869514 } } ], "vout": [ { "amount": 807122016, "target": { "key": "670a1f189330a9fcc5f5882af188751b419680c4a321abf641fe21e0d082af16" } } ], "extra": [ 1, 244, 197, 104, 57, 20, 247, 96, 23, 127, 19, 255, 161, 24, 173, 102, 111, 207, 219, 160, 66, 219, 121, 103, 215, 104, 164, 229, 247, 58, 14, 42, 184, 2, 17, 0, 0, 0, 26, 230, 210, 127, 156, 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