Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58f563240bfe76517a5f6479cc518b3dd4c60676d828bd15a4586388614981a3

Tx prefix hash: aad50743ad5daca73e464259476fd40caf7f92b5adfebf8b241eaa61fa7cf731
Tx public key: d30006c6f20145fa9d112b5f926204f7e6e34e1155f8f4ea06ce6d1c019c2c52
Timestamp: 1578440117 Timestamp [UTC]: 2020-01-07 23:35:17 Age [y:d:h:m:s]: 06:259:22:50:07
Block: 40852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1600531 RingCT/type: yes/0
Extra: 01d30006c6f20145fa9d112b5f926204f7e6e34e1155f8f4ea06ce6d1c019c2c520211000000134943cd9f000000000000000000

1 output(s) for total of 0.449408427166 xmr

stealth address amount amount idx tag
00: c377e147069bae84b35b264d4086ff3ceeb3ef45e4a002eb998eb0092ae9d1af 0.449408427166 72177 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": 40862, "vin": [ { "gen": { "height": 40852 } } ], "vout": [ { "amount": 449408427166, "target": { "key": "c377e147069bae84b35b264d4086ff3ceeb3ef45e4a002eb998eb0092ae9d1af" } } ], "extra": [ 1, 211, 0, 6, 198, 242, 1, 69, 250, 157, 17, 43, 95, 146, 98, 4, 247, 230, 227, 78, 17, 85, 248, 244, 234, 6, 206, 109, 28, 1, 156, 44, 82, 2, 17, 0, 0, 0, 19, 73, 67, 205, 159, 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: