Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 115b4940fe2aed55a52b35f209e0aab2c0c1b6b994a04b45a260f53b9ecb8622

Tx prefix hash: 60613acbaf1b777cb0ee525af3729e27b441bf68275f23ac089c9cfbb72f63e9
Tx public key: 9985146643fddec6701ac0583ba7e8bae64d22f43eeb4f165979490525e34e5a
Timestamp: 1774606705 Timestamp [UTC]: 2026-03-27 10:18:25 Age [y:d:h:m:s]: 00:238:08:00:07
Block: 1506865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175994 RingCT/type: yes/0
Extra: 019985146643fddec6701ac0583ba7e8bae64d22f43eeb4f165979490525e34e5a021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2ffe08f9ce051f4ea478fddb75f7ae65f86977cd62b8711b4c34f7cc5a862142 0.000600000000 1996613 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": 1506875, "vin": [ { "gen": { "height": 1506865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ffe08f9ce051f4ea478fddb75f7ae65f86977cd62b8711b4c34f7cc5a862142" } } ], "extra": [ 1, 153, 133, 20, 102, 67, 253, 222, 198, 112, 26, 192, 88, 59, 167, 232, 186, 230, 77, 34, 244, 62, 235, 79, 22, 89, 121, 73, 5, 37, 227, 78, 90, 2, 17, 0, 0, 0, 2, 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: