Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3b2d7c2cb60d9307f7fdbb862cb757e6b4ba6884706fc65246c63fbab98c60

Tx prefix hash: 846dbd0abdccc7639c2698d314afe6440756d296b153ab73f148240ab8618bb7
Tx public key: 48a053edd8c6fea68eb31c5f65fdb1befeeb2351f48da48dbd7136e4368622d8
Timestamp: 1760425536 Timestamp [UTC]: 2025-10-14 07:05:36 Age [y:d:h:m:s]: 01:030:13:31:50
Block: 1389600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288041 RingCT/type: yes/0
Extra: 0148a053edd8c6fea68eb31c5f65fdb1befeeb2351f48da48dbd7136e4368622d8021100000004df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ffa071d5a669d61f58324e7590ef8bf4329aabe2ac93b50cc9fc14aed81caf15 0.000600000000 1877829 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": 1389610, "vin": [ { "gen": { "height": 1389600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffa071d5a669d61f58324e7590ef8bf4329aabe2ac93b50cc9fc14aed81caf15" } } ], "extra": [ 1, 72, 160, 83, 237, 216, 198, 254, 166, 142, 179, 28, 95, 101, 253, 177, 190, 254, 235, 35, 81, 244, 141, 164, 141, 189, 113, 54, 228, 54, 134, 34, 216, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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: