Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f76a0cc36345e13371cc3d5d44fdbf5330f60c20ae63edfd02e99ce58c8f594e

Tx prefix hash: ffaeed6f53e7b31eb4f923d7bdb92f6375016f72a9d113ad61f17392035823fb
Tx public key: 226dd56b4ac016eb04d91faa8b5196d0531773c0cf66f8484eb7098fdaae5daa
Timestamp: 1773558732 Timestamp [UTC]: 2026-03-15 07:12:12 Age [y:d:h:m:s]: 00:244:14:24:50
Block: 1498207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180214 RingCT/type: yes/0
Extra: 01226dd56b4ac016eb04d91faa8b5196d0531773c0cf66f8484eb7098fdaae5daa021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ec2291ab5c4185de6337d6bbf057da6567e1a99941f7b8c600110e5c63a9d0c6 0.000600000000 1987853 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": 1498217, "vin": [ { "gen": { "height": 1498207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec2291ab5c4185de6337d6bbf057da6567e1a99941f7b8c600110e5c63a9d0c6" } } ], "extra": [ 1, 34, 109, 213, 107, 74, 192, 22, 235, 4, 217, 31, 170, 139, 81, 150, 208, 83, 23, 115, 192, 207, 102, 248, 72, 78, 183, 9, 143, 218, 174, 93, 170, 2, 17, 0, 0, 0, 5, 228, 245, 25, 63, 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: