Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9def18565447921516ef6d04f1f97ed4962891bf8d02bd3c14b8d5c1bf2a01b2

Tx prefix hash: 058235f7ecbbc539fe5e4fcb640a4e4e416ca8b74bd2f7e6ab9b55ba3e9c27fb
Tx public key: 25d4e5211d3ddbecdcbfd97ccb0069db1f3de1d47cda2cdd868a0c89b62749ba
Timestamp: 1719199036 Timestamp [UTC]: 2024-06-24 03:17:16 Age [y:d:h:m:s]: 02:150:16:34:14
Block: 1050903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 632591 RingCT/type: yes/0
Extra: 0125d4e5211d3ddbecdcbfd97ccb0069db1f3de1d47cda2cdd868a0c89b62749ba02110000000b52d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 32d2cd01b251fd5e8199f0347f1d3ae71b5b89822b62f6970e0a6c51bb19b514 0.000600000000 1521078 of 15 -

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": 1050913, "vin": [ { "gen": { "height": 1050903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32d2cd01b251fd5e8199f0347f1d3ae71b5b89822b62f6970e0a6c51bb19b514" } } ], "extra": [ 1, 37, 212, 229, 33, 29, 61, 219, 236, 220, 191, 217, 124, 203, 0, 105, 219, 31, 61, 225, 212, 124, 218, 44, 221, 134, 138, 12, 137, 182, 39, 73, 186, 2, 17, 0, 0, 0, 11, 82, 212, 126, 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: