Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c03d55c234d3a2bf8e3634d39f2beefc4522b78bb22c5daa07cbdd335009a80

Tx prefix hash: 81f97378405f4d6e0b23da6ff6e5e841263c975720f5633ece2574fc63ebefde
Tx public key: 9851d67885d3644fd83c74184fd4c28ad211b8f7e6625b24d6622fc897a178e1
Timestamp: 1788122660 Timestamp [UTC]: 2026-08-30 20:44:20 Age [y:d:h:m:s]: 00:077:11:58:38
Block: 1624594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 54939 RingCT/type: yes/0
Extra: 019851d67885d3644fd83c74184fd4c28ad211b8f7e6625b24d6622fc897a178e1

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 01b17b8fb8315cdbb8f8ddce9ffe5b1a08d8264238fa20b79a6dffc83c34598c 0.000600000000 2114614 of 15 <96>

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": 1624604, "vin": [ { "gen": { "height": 1624594 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "01b17b8fb8315cdbb8f8ddce9ffe5b1a08d8264238fa20b79a6dffc83c34598c", "view_tag": "96" } } } ], "extra": [ 1, 152, 81, 214, 120, 133, 211, 100, 79, 216, 60, 116, 24, 79, 212, 194, 138, 210, 17, 184, 247, 230, 98, 91, 36, 214, 98, 47, 200, 151, 161, 120, 225 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: