Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f0cab90dc36aff1b958fbf18a7abafb183fe07c58f3cb3e016a68421177faf1

Tx prefix hash: 6fee75de30b0edee429b1911743fb3172eec4ee3f2291d0016d72759b4ccb95e
Tx public key: 11342d0c6149266b600c35e071cd1aa154b062757b8692e4e041c261e77b92e5
Timestamp: 1675557381 Timestamp [UCT]: 2023-02-05 00:36:21 Age [y:d:h:m:s]: 02:072:05:23:50
Block: 689987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573246 RingCT/type: yes/0
Extra: 0111342d0c6149266b600c35e071cd1aa154b062757b8692e4e041c261e77b92e502110000000133af99f4000000000000000000

1 output(s) for total of 3.175313207000 dcy

stealth address amount amount idx
00: b8d541ee3f2f36f55325ffda913ea53aabe47377be14d9b77bf98ef66f689114 3.175313207000 1132693 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": 689997, "vin": [ { "gen": { "height": 689987 } } ], "vout": [ { "amount": 3175313207, "target": { "key": "b8d541ee3f2f36f55325ffda913ea53aabe47377be14d9b77bf98ef66f689114" } } ], "extra": [ 1, 17, 52, 45, 12, 97, 73, 38, 107, 96, 12, 53, 224, 113, 205, 26, 161, 84, 176, 98, 117, 123, 134, 146, 228, 224, 65, 194, 97, 231, 123, 146, 229, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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