Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392f8e99f1b7676d6925f1fc800bf1da97161c9e0e2ef88caa0c07af09c00de7

Tx prefix hash: d9d76ab0e6e687ce13fa55471ee69ae595181693b4ad61b73a1ed99b7bfbfbeb
Tx public key: f78ac02436ceb763ae60a80570328104ae1518facaa6d6df223d376364e8d1a1
Timestamp: 1741764827 Timestamp [UTC]: 2025-03-12 07:33:47 Age [y:d:h:m:s]: 01:067:15:56:53
Block: 1237537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299590 RingCT/type: yes/0
Extra: 01f78ac02436ceb763ae60a80570328104ae1518facaa6d6df223d376364e8d1a1021100000007007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2e8d76e3b800947d4e542aababd45c6d52c74fc9f2633df6b79b416c73b18ef7 0.000600000000 1724492 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": 1237547, "vin": [ { "gen": { "height": 1237537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e8d76e3b800947d4e542aababd45c6d52c74fc9f2633df6b79b416c73b18ef7" } } ], "extra": [ 1, 247, 138, 192, 36, 54, 206, 183, 99, 174, 96, 168, 5, 112, 50, 129, 4, 174, 21, 24, 250, 202, 166, 214, 223, 34, 61, 55, 99, 100, 232, 209, 161, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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: