Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddea87c97cd63db37cd284a1dea75aedd8723a5558a4b2be9f5f7771f19a2f7b

Tx prefix hash: 0853ba5887adeb012ea6a2fc62b4ac361b03ee6f0cc905f5807dac42ff08829d
Tx public key: 0a4701a5330189734197c48b74ef37240be964a46413d28820e6258d9c3e6562
Timestamp: 1749262436 Timestamp [UTC]: 2025-06-07 02:13:56 Age [y:d:h:m:s]: 01:161:11:55:48
Block: 1299600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379344 RingCT/type: yes/0
Extra: 010a4701a5330189734197c48b74ef37240be964a46413d28820e6258d9c3e656202110000000343846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 419a963a3ad03e3f7d23d8b1d3072385b2fbf994fd8a077373c4deccafc076bb 0.000600000000 1787137 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": 1299610, "vin": [ { "gen": { "height": 1299600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "419a963a3ad03e3f7d23d8b1d3072385b2fbf994fd8a077373c4deccafc076bb" } } ], "extra": [ 1, 10, 71, 1, 165, 51, 1, 137, 115, 65, 151, 196, 139, 116, 239, 55, 36, 11, 233, 100, 164, 100, 19, 210, 136, 32, 230, 37, 141, 156, 62, 101, 98, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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: