Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d8de6d32e4d857190c405a5f406b3bd67cc8d97371de7cc486e21af997266f8

Tx prefix hash: ac41641831a1c8f9e40630a7ba47cc04d41863564baeb163a6108e67d4818f6e
Tx public key: 483c35b0c0837b49a071a6e2a1791ff31c0fbb5db4f6eb0b6cad280fccb8e86c
Timestamp: 1720438651 Timestamp [UTC]: 2024-07-08 11:37:31 Age [y:d:h:m:s]: 02:136:00:56:49
Block: 1061199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622203 RingCT/type: yes/0
Extra: 01483c35b0c0837b49a071a6e2a1791ff31c0fbb5db4f6eb0b6cad280fccb8e86c021100000009e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ee77490810a7a604494e8e0288a8641db0842fa72b2ccac1334ef8efd0ba4bcc 0.000600000000 1531690 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": 1061209, "vin": [ { "gen": { "height": 1061199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee77490810a7a604494e8e0288a8641db0842fa72b2ccac1334ef8efd0ba4bcc" } } ], "extra": [ 1, 72, 60, 53, 176, 192, 131, 123, 73, 160, 113, 166, 226, 161, 121, 31, 243, 28, 15, 187, 93, 180, 246, 235, 11, 108, 173, 40, 15, 204, 184, 232, 108, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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: