Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54d41370800ae7cd3e0e1990fc3a8fc821c0d3b2f8ccc122fa28736d5e9275d4

Tx prefix hash: 0c6a51c1836d1d58e8cf200c4d0c1fd1eb7720f8221c4e72fc055528f63b9736
Tx public key: 0bd1ad8ac01cbff49e55d3b9825a8a72905cc3c227af08149a30a5afa66e32b2
Timestamp: 1742195324 Timestamp [UTC]: 2025-03-17 07:08:44 Age [y:d:h:m:s]: 01:244:19:01:06
Block: 1241110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438961 RingCT/type: yes/0
Extra: 010bd1ad8ac01cbff49e55d3b9825a8a72905cc3c227af08149a30a5afa66e32b20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fb6a353c80f676aae2396aa4fefc717f0f3084a458d4414c1f6f33e4e55a30e6 0.000600000000 1728083 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": 1241120, "vin": [ { "gen": { "height": 1241110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb6a353c80f676aae2396aa4fefc717f0f3084a458d4414c1f6f33e4e55a30e6" } } ], "extra": [ 1, 11, 209, 173, 138, 192, 28, 191, 244, 158, 85, 211, 185, 130, 90, 138, 114, 144, 92, 195, 194, 39, 175, 8, 20, 154, 48, 165, 175, 166, 110, 50, 178, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: