Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecb4ff4930edca4f12ea66b605f91c24ba2937254f7da06f27b450eb5f8e7aba

Tx prefix hash: f86594987f24e08e8df7ac2206d30d31e6bbda93e94e3d9555407746b271b527
Tx public key: 6e0523327fc1a3bfec57b2845c55bac385bc5623d5fd5fe25c74c41159168d02
Timestamp: 1760895467 Timestamp [UTC]: 2025-10-19 17:37:47 Age [y:d:h:m:s]: 01:025:20:27:15
Block: 1393494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284689 RingCT/type: yes/0
Extra: 016e0523327fc1a3bfec57b2845c55bac385bc5623d5fd5fe25c74c41159168d0202110000000525a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3944cdf18885a7d8eeafb7b1753fdc41feea737cd7ccb8dc5febc362a6566ea9 0.000600000000 1881759 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": 1393504, "vin": [ { "gen": { "height": 1393494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3944cdf18885a7d8eeafb7b1753fdc41feea737cd7ccb8dc5febc362a6566ea9" } } ], "extra": [ 1, 110, 5, 35, 50, 127, 193, 163, 191, 236, 87, 178, 132, 92, 85, 186, 195, 133, 188, 86, 35, 213, 253, 95, 226, 92, 116, 196, 17, 89, 22, 141, 2, 2, 17, 0, 0, 0, 5, 37, 163, 90, 15, 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: