Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc42c71f16e16f0d2ed8d98452e27f3cbd5dc55dc44ed0baea912fa965828541

Tx prefix hash: 0be419a9c5ce1c4375b1bbc7673207151c418fcd6cc297fdf8f8972245e8c00d
Tx public key: 4c97163beebe94315361c3583915e7e99918cb4990f8cea0ef32d77f5e352605
Timestamp: 1773986129 Timestamp [UTC]: 2026-03-20 05:55:29 Age [y:d:h:m:s]: 00:240:03:01:47
Block: 1501716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177065 RingCT/type: yes/0
Extra: 014c97163beebe94315361c3583915e7e99918cb4990f8cea0ef32d77f5e352605021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3ee0eed5fcbd4bf1d731b328b3fa66f1eff776408acf70d50939cb3cc16ab6f8 0.000600000000 1991402 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": 1501726, "vin": [ { "gen": { "height": 1501716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ee0eed5fcbd4bf1d731b328b3fa66f1eff776408acf70d50939cb3cc16ab6f8" } } ], "extra": [ 1, 76, 151, 22, 59, 238, 190, 148, 49, 83, 97, 195, 88, 57, 21, 231, 233, 153, 24, 203, 73, 144, 248, 206, 160, 239, 50, 215, 127, 94, 53, 38, 5, 2, 17, 0, 0, 0, 2, 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: