Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00525c7f67fd8ee81a6dbd282632f4cd6321351fda4824db6220981190bad4e9

Tx prefix hash: e85d3ba0d11b0a694cd43999db471c1f715622cb122f5a033887d60ba68a027e
Tx public key: 49e96ada8976e609b75b0d3556b0b99548de1e6bdea0f4cfaef6b35cfb8dd781
Timestamp: 1651443561 Timestamp [UTC]: 2022-05-01 22:19:21 Age [y:d:h:m:s]: 04:115:13:58:54
Block: 492350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1127583 RingCT/type: yes/0
Extra: 0149e96ada8976e609b75b0d3556b0b99548de1e6bdea0f4cfaef6b35cfb8dd78102110000000ca8c141c5000000000000000000

1 output(s) for total of 0.014343009383 xmr

stealth address amount amount idx tag
00: beffca94cb9fc6cf0a57b55cb48e52ff8c6a86a2b02ee9d6c834500d3fccb36e 0.014343009383 915677 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": 492360, "vin": [ { "gen": { "height": 492350 } } ], "vout": [ { "amount": 14343009383, "target": { "key": "beffca94cb9fc6cf0a57b55cb48e52ff8c6a86a2b02ee9d6c834500d3fccb36e" } } ], "extra": [ 1, 73, 233, 106, 218, 137, 118, 230, 9, 183, 91, 13, 53, 86, 176, 185, 149, 72, 222, 30, 107, 222, 160, 244, 207, 174, 246, 179, 92, 251, 141, 215, 129, 2, 17, 0, 0, 0, 12, 168, 193, 65, 197, 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: