Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01d51f12566a5d1046e2dae9c542f8bccec8a794278ae5c5d800a9d7838c6528

Tx prefix hash: 52e59c81d82f58b3cb178acd1248189ba74a3b9ecca4307e5cfddcdf05e6e6a5
Tx public key: 1e28824f07f51af1739e59a051c6a9fe308a09807435ff7a1cee32b71fa217c0
Timestamp: 1774668979 Timestamp [UTC]: 2026-03-28 03:36:19 Age [y:d:h:m:s]: 00:239:10:00:18
Block: 1507382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176112 RingCT/type: yes/0
Extra: 011e28824f07f51af1739e59a051c6a9fe308a09807435ff7a1cee32b71fa217c0021100000005f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 442f75bb6e870e7d47a8f61b8d20c34a1ec1fda5d9685976d2e7b6864e2b2ea3 0.000600000000 1997134 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": 1507392, "vin": [ { "gen": { "height": 1507382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "442f75bb6e870e7d47a8f61b8d20c34a1ec1fda5d9685976d2e7b6864e2b2ea3" } } ], "extra": [ 1, 30, 40, 130, 79, 7, 245, 26, 241, 115, 158, 89, 160, 81, 198, 169, 254, 48, 138, 9, 128, 116, 53, 255, 122, 28, 238, 50, 183, 31, 162, 23, 192, 2, 17, 0, 0, 0, 5, 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: