Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df6958aaea73feae6eb269878cdd2748b5581152b204d7ffc694358ce03dab0b

Tx prefix hash: 71995a27856f444a0a84437e6bb4ed987c8fd5e12efaa0fd31e2a7c626c27efb
Tx public key: d6ac9863fb9000031d7b39d987f1debb30b9c7e9e6a996c76696ea9ffb90e933
Timestamp: 1584634617 Timestamp [UTC]: 2020-03-19 16:16:57 Age [y:d:h:m:s]: 06:248:09:44:22
Block: 85436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1598058 RingCT/type: yes/0
Extra: 01d6ac9863fb9000031d7b39d987f1debb30b9c7e9e6a996c76696ea9ffb90e93302110000003d69b04ac4000000000000000000

1 output(s) for total of 0.319827532759 xmr

stealth address amount amount idx tag
00: 7b1d0db66afbb706c4a052e92cb6417a173a5fedc5013412aeab6c5a288f6d9a 0.319827532759 154456 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": 85446, "vin": [ { "gen": { "height": 85436 } } ], "vout": [ { "amount": 319827532759, "target": { "key": "7b1d0db66afbb706c4a052e92cb6417a173a5fedc5013412aeab6c5a288f6d9a" } } ], "extra": [ 1, 214, 172, 152, 99, 251, 144, 0, 3, 29, 123, 57, 217, 135, 241, 222, 187, 48, 185, 199, 233, 230, 169, 150, 199, 102, 150, 234, 159, 251, 144, 233, 51, 2, 17, 0, 0, 0, 61, 105, 176, 74, 196, 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: