Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c2ad13c19b64fe57dfe0d8149a455c189e04f4bb68cfffd4d7c93ea46c0e745

Tx prefix hash: 0a4cdd9f4862e4a3ace7853dec69f7b635e71cf9f22711ead48014b6458ef33d
Tx public key: 4df8268328bbbc0ee60e4d35ca4585bfd8e22541c392b7fd7baa2f28d721c13e
Timestamp: 1757855420 Timestamp [UTC]: 2025-09-14 13:10:20 Age [y:d:h:m:s]: 01:067:21:52:24
Block: 1368287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315079 RingCT/type: yes/0
Extra: 014df8268328bbbc0ee60e4d35ca4585bfd8e22541c392b7fd7baa2f28d721c13e021100000004b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f1503a3ddbdfef1ace4c1d5326dfa13e5a85213cc347ac429a897fa3235fc21e 0.000600000000 1856330 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": 1368297, "vin": [ { "gen": { "height": 1368287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1503a3ddbdfef1ace4c1d5326dfa13e5a85213cc347ac429a897fa3235fc21e" } } ], "extra": [ 1, 77, 248, 38, 131, 40, 187, 188, 14, 230, 14, 77, 53, 202, 69, 133, 191, 216, 226, 37, 65, 195, 146, 183, 253, 123, 170, 47, 40, 215, 33, 193, 62, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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: