Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52396fd3af3e080a7642bbde86d32c18c2bb514f804c6a471a547e93781006a

Tx prefix hash: ff9c2d90e622786e1dff5dcd79bd8ff3a8bcea1b53144d9795fb3a897fbb6dd9
Tx public key: badd1e6f9c83f09993f7e0093494e3657813f0ef2660b0f2ab0ff1cfbb318c33
Timestamp: 1747381106 Timestamp [UTC]: 2025-05-16 07:38:26 Age [y:d:h:m:s]: 00:364:20:44:32
Block: 1284018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250845 RingCT/type: yes/0
Extra: 01badd1e6f9c83f09993f7e0093494e3657813f0ef2660b0f2ab0ff1cfbb318c330211000000031f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 633853135a33f4fa259b8f27cb97a91234d16c41c64c188b4fec9fa96bc9c9a3 0.000600000000 1771453 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": 1284028, "vin": [ { "gen": { "height": 1284018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "633853135a33f4fa259b8f27cb97a91234d16c41c64c188b4fec9fa96bc9c9a3" } } ], "extra": [ 1, 186, 221, 30, 111, 156, 131, 240, 153, 147, 247, 224, 9, 52, 148, 227, 101, 120, 19, 240, 239, 38, 96, 176, 242, 171, 15, 241, 207, 187, 49, 140, 51, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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: