Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4ef2d619a2a5ff0c1a9f44d1c8bee99262549bc5a4e0f2f439d15bfe7fd2ed7

Tx prefix hash: 259089c332df835568f5564adcc96b2538fa22fcc4b29e3b259c915c0aa51ec7
Tx public key: b63f07a3a9a63d135b434e0bc8c1607846b58d03e8865a5b19b5d39579a84698
Timestamp: 1775190194 Timestamp [UTC]: 2026-04-03 04:23:14 Age [y:d:h:m:s]: 00:228:12:04:13
Block: 1511694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168799 RingCT/type: yes/0
Extra: 01b63f07a3a9a63d135b434e0bc8c1607846b58d03e8865a5b19b5d39579a8469802110000000243b50471000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7a7107e35f2ea6f721a5817c6f483da5c7017d8e9160c2fb710ace11a8cce04d 0.000600000000 2001488 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": 1511704, "vin": [ { "gen": { "height": 1511694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a7107e35f2ea6f721a5817c6f483da5c7017d8e9160c2fb710ace11a8cce04d" } } ], "extra": [ 1, 182, 63, 7, 163, 169, 166, 61, 19, 91, 67, 78, 11, 200, 193, 96, 120, 70, 181, 141, 3, 232, 134, 90, 91, 25, 181, 211, 149, 121, 168, 70, 152, 2, 17, 0, 0, 0, 2, 67, 181, 4, 113, 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: