Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10aef318bd7b5b85f8a58d02d7e430e2adf6d7aa19c123fe3274c76987c4decc

Tx prefix hash: 3c072ff851f02440a29285a4a14ff61e4971f813a32aa69dcffd2c76bb1c1d9c
Tx public key: 8d6003640b09f49e4afffabb02d8cb72bd1bd54873baf003788610c18dabf369
Timestamp: 1645823688 Timestamp [UCT]: 2022-02-25 21:14:48 Age [y:d:h:m:s]: 03:016:15:08:58
Block: 446450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 791959 RingCT/type: yes/0
Extra: 018d6003640b09f49e4afffabb02d8cb72bd1bd54873baf003788610c18dabf369021100000036cb8520c2000000000000000000

1 output(s) for total of 20.357577826000 dcy

stealth address amount amount idx
00: 1e0bc80dfa2d997225b95b8efb86dbf97c6f189bfec8c764fd4c5cf5c14ad4e4 20.357577826000 860341 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": 446460, "vin": [ { "gen": { "height": 446450 } } ], "vout": [ { "amount": 20357577826, "target": { "key": "1e0bc80dfa2d997225b95b8efb86dbf97c6f189bfec8c764fd4c5cf5c14ad4e4" } } ], "extra": [ 1, 141, 96, 3, 100, 11, 9, 244, 158, 74, 255, 250, 187, 2, 216, 203, 114, 189, 27, 213, 72, 115, 186, 240, 3, 120, 134, 16, 193, 141, 171, 243, 105, 2, 17, 0, 0, 0, 54, 203, 133, 32, 194, 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