Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f16feed2f32dba60c023d289b319fbf1dfac368f2bae16b1a1eed6c239cf58c0

Tx prefix hash: d0e1a83b9bf1484680b5a6d8fc21c3bd8d498f868f08acfa9c6950a1218d49c7
Tx public key: 1364cedefccc9ad367abb20758a8c16a27591e498b40754ed3aaecfc4d4aa60f
Timestamp: 1579800194 Timestamp [UTC]: 2020-01-23 17:23:14 Age [y:d:h:m:s]: 06:301:23:08:30
Block: 51671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1630342 RingCT/type: yes/0
Extra: 011364cedefccc9ad367abb20758a8c16a27591e498b40754ed3aaecfc4d4aa60f021100000007ff58ae94000000000000000000

1 output(s) for total of 0.413829976051 xmr

stealth address amount amount idx tag
00: 84851a0b17e75a17f224d9c7f5be914c19b2cf751ed92e40a897896dacc22c96 0.413829976051 95761 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": 51681, "vin": [ { "gen": { "height": 51671 } } ], "vout": [ { "amount": 413829976051, "target": { "key": "84851a0b17e75a17f224d9c7f5be914c19b2cf751ed92e40a897896dacc22c96" } } ], "extra": [ 1, 19, 100, 206, 222, 252, 204, 154, 211, 103, 171, 178, 7, 88, 168, 193, 106, 39, 89, 30, 73, 139, 64, 117, 78, 211, 170, 236, 252, 77, 74, 166, 15, 2, 17, 0, 0, 0, 7, 255, 88, 174, 148, 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) | monero version: