Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0d6268a1ec1f8330713d61af17bf14e06f6c25ec4a98a7c13bdddeca4cf47bb

Tx prefix hash: 129318ccad6d0dfc8bed31188c1bc8970931113074d52676c2c1b292d0f93605
Tx public key: 5f1c19ec63245d5cba0de4d374e9f620eada43f07679161986efb82ea8fd22a7
Timestamp: 1747328143 Timestamp [UTC]: 2025-05-15 16:55:43 Age [y:d:h:m:s]: 00:364:22:37:29
Block: 1283584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250867 RingCT/type: yes/0
Extra: 015f1c19ec63245d5cba0de4d374e9f620eada43f07679161986efb82ea8fd22a70211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 52322647adb6ebd5f4ab88dd4b4389312163666bd16e8172ae310eb93e3b3af5 0.000600000000 1771003 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": 1283594, "vin": [ { "gen": { "height": 1283584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52322647adb6ebd5f4ab88dd4b4389312163666bd16e8172ae310eb93e3b3af5" } } ], "extra": [ 1, 95, 28, 25, 236, 99, 36, 93, 92, 186, 13, 228, 211, 116, 233, 246, 32, 234, 218, 67, 240, 118, 121, 22, 25, 134, 239, 184, 46, 168, 253, 34, 167, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: