Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ba50ce38ca0cde8f5f12ae160448d9a9ae681c782574b9e4fa98f0c8b03692c

Tx prefix hash: 36c06d20c65bab7ff39fd189e5ea1a4269abc94e48b0461b3febb609ab71d5b8
Tx public key: 6c3c2e9f0e874c74ccd50c9d337567994f35a17e406db8a6ab569c5a30b8377b
Timestamp: 1738993805 Timestamp [UTC]: 2025-02-08 05:50:05 Age [y:d:h:m:s]: 01:284:04:30:18
Block: 1214590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467222 RingCT/type: yes/0
Extra: 016c3c2e9f0e874c74ccd50c9d337567994f35a17e406db8a6ab569c5a30b8377b021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3f51096b59fe923f2009bb735aebbaff0f91cdb1ba3309e304e709d8a190e45e 0.000600000000 1701381 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": 1214600, "vin": [ { "gen": { "height": 1214590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f51096b59fe923f2009bb735aebbaff0f91cdb1ba3309e304e709d8a190e45e" } } ], "extra": [ 1, 108, 60, 46, 159, 14, 135, 76, 116, 204, 213, 12, 157, 51, 117, 103, 153, 79, 53, 161, 126, 64, 109, 184, 166, 171, 86, 156, 90, 48, 184, 55, 123, 2, 17, 0, 0, 0, 1, 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: