Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc98c4f042e7fcbb782ed41764355eecb0a57b3f96a8a41efac44c64b0234e0e

Tx prefix hash: 50de8f44b3a1641311c1d05891fa5e94c02e91735cfd2eb9f32fd11c2d632a20
Tx public key: 08000d8f711bf3af9cbbe6a7ca4c36e52a0a5d17ab2af9257fe76726081cf784
Timestamp: 1580049902 Timestamp [UTC]: 2020-01-26 14:45:02 Age [y:d:h:m:s]: 06:026:05:23:06
Block: 53386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1428041 RingCT/type: yes/0
Extra: 0108000d8f711bf3af9cbbe6a7ca4c36e52a0a5d17ab2af9257fe76726081cf784021100000003dcee4b4d000000000000000000

1 output(s) for total of 0.408448658242 xmr

stealth address amount amount idx tag
00: f2105a4dc2e82d5db41e0ae4438667ddc9f6e13e7160aea20f605c48a624ca4a 0.408448658242 98956 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 dinastycoin-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": 53396, "vin": [ { "gen": { "height": 53386 } } ], "vout": [ { "amount": 408448658242, "target": { "key": "f2105a4dc2e82d5db41e0ae4438667ddc9f6e13e7160aea20f605c48a624ca4a" } } ], "extra": [ 1, 8, 0, 13, 143, 113, 27, 243, 175, 156, 187, 230, 167, 202, 76, 54, 229, 42, 10, 93, 23, 171, 42, 249, 37, 127, 231, 103, 38, 8, 28, 247, 132, 2, 17, 0, 0, 0, 3, 220, 238, 75, 77, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369