Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54e0c7ea2b18f8d063e6623ec759f3564a0fa5fc1d27a0b3cc37a6570ef0a812

Tx prefix hash: 02976487f105ed66779a9cdc57028d1a66073bfb604404f8075d217f4e5755b3
Tx public key: 7d6ff2d366bfb226374f4124d8affce8575ca2e47b5f7a9a09a16662de12ecd6
Timestamp: 1774534944 Timestamp [UTC]: 2026-03-26 14:22:24 Age [y:d:h:m:s]: 00:239:08:24:59
Block: 1506270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176717 RingCT/type: yes/0
Extra: 017d6ff2d366bfb226374f4124d8affce8575ca2e47b5f7a9a09a16662de12ecd6021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 29b6b5021f23d29c71e68492cbc941568fead04dc8b4608a4ba851fdefcb5272 0.000600000000 1996014 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": 1506280, "vin": [ { "gen": { "height": 1506270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29b6b5021f23d29c71e68492cbc941568fead04dc8b4608a4ba851fdefcb5272" } } ], "extra": [ 1, 125, 111, 242, 211, 102, 191, 178, 38, 55, 79, 65, 36, 216, 175, 252, 232, 87, 92, 162, 228, 123, 95, 122, 154, 9, 161, 102, 98, 222, 18, 236, 214, 2, 17, 0, 0, 0, 3, 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: