Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 628e626ba9e17af18db4ad392e00a5e067080b71a0c63e9e8d3584dbe28d901b

Tx prefix hash: 6290749bd24cdb6a9146b5dc16117b799e8e005ec68ecbca19171805f129e58f
Tx public key: 5e69e2e940d2485fdc0bc77f52d08ee0f30c3b1a8d418fe0674259a75855d1ba
Timestamp: 1746252318 Timestamp [UTC]: 2025-05-03 06:05:18 Age [y:d:h:m:s]: 01:201:19:09:07
Block: 1274684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408386 RingCT/type: yes/0
Extra: 015e69e2e940d2485fdc0bc77f52d08ee0f30c3b1a8d418fe0674259a75855d1ba0211000000129f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fa930827cc3ba97172752e7e9ddf4d6ae076499b2b0cba347c0ecf0aa36208d3 0.000600000000 1761983 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": 1274694, "vin": [ { "gen": { "height": 1274684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa930827cc3ba97172752e7e9ddf4d6ae076499b2b0cba347c0ecf0aa36208d3" } } ], "extra": [ 1, 94, 105, 226, 233, 64, 210, 72, 95, 220, 11, 199, 127, 82, 208, 142, 224, 243, 12, 59, 26, 141, 65, 143, 224, 103, 66, 89, 167, 88, 85, 209, 186, 2, 17, 0, 0, 0, 18, 159, 159, 230, 140, 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: