Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b57ad2d973bdf3f0c09c5bd1c596328dd5e366f5c9553b4db23eccb308428c1e

Tx prefix hash: e1159e4aa070d1aca2ac35f6d67e01203021bbafc7620250e87fbe2327d45b43
Tx public key: d66111261310aa342fea7d4680562e3c7903ec6762bb45de476b81fc1eabfa3f
Timestamp: 1741114457 Timestamp [UTC]: 2025-03-04 18:54:17 Age [y:d:h:m:s]: 01:261:16:48:30
Block: 1232146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451239 RingCT/type: yes/0
Extra: 01d66111261310aa342fea7d4680562e3c7903ec6762bb45de476b81fc1eabfa3f02110000000a007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 708a5084b424e0a3c5ea6148375e5b4f592bee58d5bd3b85566860f5992b85e2 0.000600000000 1719059 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": 1232156, "vin": [ { "gen": { "height": 1232146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "708a5084b424e0a3c5ea6148375e5b4f592bee58d5bd3b85566860f5992b85e2" } } ], "extra": [ 1, 214, 97, 17, 38, 19, 16, 170, 52, 47, 234, 125, 70, 128, 86, 46, 60, 121, 3, 236, 103, 98, 187, 69, 222, 71, 107, 129, 252, 30, 171, 250, 63, 2, 17, 0, 0, 0, 10, 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: