Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 920befec9b06fcb780481e173b0fb35e4b173cd3348bfbf60a0a48d7b15db39b

Tx prefix hash: bb942ce41913a0bbf46b3b37f9de441418820f59be406738a318389f23694af1
Tx public key: 72645b58827e5e59fa9245b51b4b27bd2e0efbda627b2c4d76fea0ec86e94ab2
Timestamp: 1774208300 Timestamp [UTC]: 2026-03-22 19:38:20 Age [y:d:h:m:s]: 00:238:18:06:03
Block: 1503556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176127 RingCT/type: yes/0
Extra: 0172645b58827e5e59fa9245b51b4b27bd2e0efbda627b2c4d76fea0ec86e94ab2021100000009f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 102cd75373fbf40abde2c116d496648cfc6e859933d17334d19ce049cf964b7b 0.000600000000 1993268 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": 1503566, "vin": [ { "gen": { "height": 1503556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "102cd75373fbf40abde2c116d496648cfc6e859933d17334d19ce049cf964b7b" } } ], "extra": [ 1, 114, 100, 91, 88, 130, 126, 94, 89, 250, 146, 69, 181, 27, 75, 39, 189, 46, 14, 251, 218, 98, 123, 44, 77, 118, 254, 160, 236, 134, 233, 74, 178, 2, 17, 0, 0, 0, 9, 241, 136, 200, 168, 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: